Crawlora MCP

ebay_search

Read-only

Search eBay listings by keyword, with optional category and pagination inputs. Results contain normalized listing cards; use this to discover items before opening a specific listing for more detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ebay_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	Result page number, default 1.
`limit`	No	Results per page, default 60. Allowed values: 60, 120, 240.
`keyword`	No	eBay search keyword (required).
`listing_type`	No	Listing status filter, default active. Allowed values: active, sold, completed, sold_completed.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-reach behavior are covered. The description adds that results are 'normalized listing cards', a small useful detail, but says nothing about rate limits, ranking, or result caps beyond what the schema documents.

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?

Two short sentences, purpose lead, usage second — well front-loaded with no filler. The stray 'category' mention is a small inaccuracy rather than bloat.

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 an output schema present and annotations covering safety, the description only needs to convey purpose and when-to-use, which it does. The only gap is the inaccurate 'category' reference and no note on which filter fields exist.

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 coverage is 100%, so baseline is 3. The description references keyword and pagination, which map to real params, but it also mentions an 'optional category' input that does not exist in the schema (the filter param is listing_type), so it adds no accurate meaning beyond the schema.

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 ('Search eBay listings by keyword') and names the downstream sibling action ('opening a specific listing for more detail'), letting an agent distinguish it from ebay_item without opening either schema.

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

Usage Guidelines4/5

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

Explicitly frames the tool as a discovery step that precedes opening an individual listing, which is real when-to-use guidance. It stops short of naming ebay_item directly or stating exclusions, so it is not a full 5.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?