Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

VS Code Marketplace Extension & Publisher Scraper

scrape_vscode_marketplace_extensions
Read-onlyIdempotent

Scrape VS Code Marketplace extensions by keyword to collect install counts, ratings, GitHub repo links, and publisher details for developer tool market research.

Instructions

Extract VS Code extension install counts, ratings, GitHub repo links, and developer/company publisher details by keyword ($0.50/1k).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "queries": "<queries>"
    },
    "name": "scrape_vscode_marketplace_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesSearch keywords, e.g. ["copilot", "mcp", "terraform"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered without description help. The description adds genuinely new context by disclosing pricing ($0.50/1k), which is a distinct behavioral consideration when deciding to invoke it. It stops short of mentioning throttling, result caps, or pagination.

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?

A single front-loaded sentence that lists the returned data first and the cost last, with no filler. Slightly dense prose, but every clause carries information an agent can act on.

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?

For a one-parameter, read-only scraper with strong annotations, the description is nearly sufficient, and enumerating the extracted fields effectively substitutes for the absent output schema. The main remaining gap is any hint about volume limits or how many results a keyword set produces.

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?

The single parameter has 100% schema description coverage with an example, so baseline is 3. The phrase 'by keyword' and the per-1k pricing hint at per-query billing but add no syntax or format detail beyond what the schema already documents.

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

Purpose4/5

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

The definition uses a specific verb ('Extract') with a named resource ('VS Code extension install counts, ratings, GitHub repo links, and developer/company publisher details') scoped by keyword. That level of specificity tells an agent exactly what data comes back, though it does not name a sibling to differentiate from (e.g. spy_chrome_firefox_extensions).

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?

Usage is only implied through the extracted fields and the keyword-driven input, signalling a lead-generation or market-research purpose. There is no explicit statement of when to choose this over an alternative extension scraper or when-not to use it.

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