Eclipse Marketplace Plugins Search Scraper is a BrowserAct Bot template for collecting structured public plugin and solution records from Eclipse Marketplace. Configure a base URL, keyword, and result count, then run the Bot to return ranked marketplace listings for developer tooling research, plugin discovery, ecosystem monitoring, catalog enrichment, or automation workflows.
What Does BrowserAct Eclipse Marketplace Plugins Search Scraper Do?
This template opens Eclipse Marketplace's public search results, reads listing cards across result pages, and returns one structured record per plugin or solution.
Key Features
- Extract public Eclipse Marketplace search results without requiring a login.
- Capture plugin name, URL, summary, provider, category, review count, update date, and keyword.
- Keep optional install count, rating, and tag fields available when visible.
- Page through public result pages until the requested count is reached.
- Handle empty result pages cleanly.
What Data Can I Extract from Eclipse Marketplace?
| Field | Description |
|---|---|
rank |
Search result position assigned by the Bot. |
plugin_name |
Plugin or solution listing name. |
plugin_url |
Public Eclipse Marketplace listing URL. |
summary |
Listing summary or description snippet. |
provider |
Provider, company, or author shown on the listing card. |
category |
Category values shown on the search card. |
install_count |
Install or download count when visible. |
rating |
Star rating when visible. |
review_count |
Review or comment count shown on the card. |
tags |
Tags when visible. |
last_updated |
Last updated date shown on the listing card. |
search_keyword |
Keyword used for the run. |
How to Use Eclipse Marketplace Plugins Search Scraper
- Click Run task.
- Enter the Eclipse Marketplace base URL.
- Enter a plugin, framework, language, platform, or tooling keyword.
- Set how many listing records to collect.
- Run the Bot and review the structured plugin results.
- Reuse the Bot with another keyword or connect the output to your workflow.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
base_url |
Yes | https://marketplace.eclipse.org |
Eclipse Marketplace base URL without a trailing slash. |
keyword |
Yes | java |
Search keyword used to find public listings. |
count |
Yes | 20 |
Maximum number of plugin or solution records to collect. |
Example Output
The table below uses records preserved from the validated Bot run. Up to the first 5 records are shown, and long values are shortened in this documentation preview.
| rank | plugin_name | plugin_url | summary | provider | category | install_count | rating | review_count | tags | last_updated | search_keyword |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Java Antidecompiler | https://marketplace.eclipse.org/content/java-antidecompiler | Absolute Java code and resources protection tool at the binary level... | Yury Bendersky | Build and Deploy, Code Management, Tools | null | null | 11 | null | Sunday, July 6, 2025 - 08:04 | java |
How Does it Work?
BrowserAct builds the working public Eclipse Marketplace search URL in the format {base_url}/search?search_api_fulltext={keyword}&page=0. Search results are shown as public listing cards, with ten records per page.
For each listing card, BrowserAct maps visible fields into a flat record, resolves the listing URL, assigns a global rank, and advances through page=1, page=2, and later pages until the requested count is reached or a page has no listing cards.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the Data You Need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Paste a clear request that includes the website, the records to collect, the filters or search conditions, the fields to return, the result limit, and the inputs you want to reuse later.
Step 2: Let BrowserAct Build and Test the Bot
BrowserAct explores the live website, works out the navigation and extraction path, and validates the result. If BrowserAct asks for clarification, reply in the same build conversation with the missing URL, condition, field, example, or expected output.
Step 3: Run the Bot and Review the Result
When the build is complete, run the Bot with the default inputs first. Review the structured records, source URLs, missing fields, and row count before reusing the Bot with new inputs or connecting it to another workflow.
Why Scrape Eclipse Marketplace Plugin Results?
Eclipse Marketplace data helps teams discover developer tools, compare plugin categories, monitor ecosystem activity, enrich internal catalogs, and route public plugin metadata into dashboards, alerts, or agent workflows.
Who Can Use This Template?
- Eclipse developers researching plugins and add-ons.
- DevRel teams monitoring plugin ecosystems.
- Product teams comparing developer tooling categories.
- Platform teams enriching internal software catalogs.
- Automation builders routing plugin metadata into spreadsheets, databases, alerts, or agents.
How Many Results Can You Scrape?
Use count to control the number of listing records returned. The Bot reads ten records per public result page and continues through available pages until it reaches the requested count or no more public results are available.
Automation and Export
BrowserAct returns structured Eclipse Marketplace listing records first. You can then use the output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual CSV review.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com
