Skip to main content
Glama
Sign In
ceadigital-mcp-tools

ceadigital-mcp-tools

Official
by ceadigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

ebay_sold_listings_comps_scraper

Calculate 90-day eBay sold comps medians, IQR-filtered price spread, sell-through rate, and net margin after fees for a product query.

Instructions

Compute 90-day realized sold medians, IQR outlier-filtered spread, sell-through rate, and net margin after eBay fees. (Free 1-row preview automatic when CEA_API_KEY is unset; Apify: cea_digital/ebay-sold-listings-comps-scraper)

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": {
      "query": "<query>"
    },
    "name": "ebay_sold_listings_comps_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPrimary target query, domain, URL, or identifier (default: "Fujifilm X100V Silver Digital Camera")Fujifilm X100V Silver Digital Camera
secondaryNoOptional secondary filter (address, condition, permit type, role keyword, or language).used

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 disclosure burden, and it does add real behavior: a free 1-row preview is returned automatically when CEA_API_KEY is unset, and the backing actor is named. However, it omits cost/credit consumption, latency, failure modes, and how the fee/margin calculation is parameterized, which matters for a scraping-and-computation tool.

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 delivers the output contract immediately, followed by a short parenthetical on preview behavior and provenance. Tight and waste-free, though the parenthetical mixes an operational caveat with a bare actor identifier that reads as a footnote rather than guidance.

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

Completeness3/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 must explain returns, and naming the four computed metrics does that partially. It still leaves the response shape (single object vs. per-listing rows), the preview's exact contents, and auth/credit requirements under-specified for a two-parameter scraping tool with zero annotations.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description goes slightly further by framing the tool around eBay sold listings, which clarifies that 'query' should be a product/keyword search rather than an arbitrary identifier despite the schema's generic 'domain, URL, or identifier' wording. It still says nothing about how 'secondary' maps to condition filtering in this eBay context.

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 ('compute') and a precise resource/output set: 90-day realized sold medians, IQR outlier-filtered spread, sell-through rate, and net margin after eBay fees. An agent can immediately tell this is an eBay sold-comps analytics tool and distinguish it from every listed sibling, which cover permits, maps, jobs, transcripts, Shopify, email validation, and skip tracing.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The metrics listed imply a pricing/valuation use case, but nothing tells the agent under what conditions to prefer this over a generic search tool or what inputs make it inappropriate.

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