Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Chrome & Firefox Extension Store Publisher Spy

spy_chrome_firefox_extensions
Read-onlyIdempotent

Extract active users, ratings, versions, and publisher support emails for Chrome and Firefox extensions by keyword or slug to research competitors and validate leads.

Instructions

Extract browser extension active users, ratings, versions, and publisher support emails by keyword or slug ($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": "spy_chrome_firefox_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesKeywords or extension slugs, e.g. ["seo", "crm"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new information the annotations do not: the cost rate ($0.50/1k) and the specific data fields returned, which matters for a paid scraping tool; it stops short of describing batching or rate limits for the query array.

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

Conciseness5/5

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

One sentence that front-loads the returned fields, then the input mode, then the price. No redundant clauses and nothing buried.

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 tool with rich annotations, the description covers what it returns and what it costs, which is what an agent most needs when deciding to spend money on it. Missing only guidance on result limits or how multiple queries are handled, which is a minor gap given there is no output schema.

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% and the single 'queries' parameter is documented in the schema with an example array. The description restates that it accepts 'keyword or slug' but adds no syntax, batch-size, or per-query semantics beyond what the schema already provides, so baseline 3 applies.

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?

Names a specific verb ('Extract') and concrete resources: active users, ratings, versions, and publisher support emails from the Chrome & Firefox extension stores. The stated source ('browser extension') plus the title distinguishes it from the VSCode marketplace sibling, though no alternative is named explicitly.

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?

The phrase 'by keyword or slug' implies the input mode, and the pricing note hints at paid/bulk usage, but there is no explicit when-to-use or when-to-prefer-a-sibling guidance and no statement of prerequisites or limits.

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