Skip to main content
Glama
paulet4a-commits

WebDataTools Developer, app & research data MCP server

by paulet4a-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

vscode_marketplace_extensions

Fetch VS Code Marketplace extension data by ID, URL, or keyword, returning installs, ratings, version, categories, tags, repository, and license in one row per extension.

Instructions

VS Code Marketplace Extension Scraper returns installs, ratings, version, categories, tags, repository and license for any VS Code extension id, marketplace URL or search keyword — one row per extension. Billed to your own Apify account: ~$0.0015 per result (Apify free-plan price, lower on paid plans).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queriesYesExtensions or searches — Enter what to look up, one row is returned per matched extension. Three formats work: an extension id like ms-python.python, a full marketplace URL like https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode, or search:<keyword> (e.g. search:prettier) to return the top matching extensions for that keyword. Example: ["ms-python.python"].
searchLimitNoSearch result limit — Enter the maximum number of extensions to return per search:<keyword> entry, e.g. 25. Extension id and URL lookups always return exactly one row and ignore this setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It usefully discloses billing behavior ('Billed to your own Apify account: ~$0.0015 per result') and row cardinality, but omits authentication requirements, rate limits, and failure modes for invalid ids.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence front-loads the returned fields, followed by pricing. Efficient, though the pricing clause is secondary and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly enumerates the returned fields and per-row granularity, which is what an agent needs to interpret results. Missing only auth/billing-setup details for the Apify account.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the three accepted query formats and the searchLimit semantics are already fully documented in the schema. The description's 'one row per extension' adds a small cardinality hint but nothing the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('returns installs, ratings, version, categories, tags, repository and license') scoped to VS Code extensions, which clearly separates it from sibling store scrapers like chrome_web_store_extensions and app_store_lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when the tool applies (lookup by id, URL, or keyword) but never states when to choose it over siblings or what prerequisites exist. No explicit when/when-not guidance or alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools