Fetch normalized details for a public eBay listing by item ID, returning clean JSON for product research, price checks, or catalog enrichment.
Get eBay item details. Returns normalized details for a public eBay item listing.
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes | eBay item ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavioral traits. It mentions 'returns normalized details' but omits specifics like authentication, rate limits, side effects, or response structure. The term 'normalized' is vague.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loaded with the action ('Get eBay item details'), and includes no unnecessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool, the description provides a basic outline but lacks details about what 'normalized details' include. Without an output schema, more specificity (e.g., fields, examples) would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'item_id' with a description 'eBay item ID'. The description does not add further meaning beyond the schema, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Get eBay item details' with a clear verb and resource, and it distinguishes from sibling tools like ebay_search (which searches for items) and ebay_seller (seller info). It focuses on retrieving a single item's details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when you have an item ID but does not explicitly state when to use this tool vs alternatives like ebay_search or ebay_seller. No guidance on prerequisites or context is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.