Fetch normalized details for a public eBay seller profile using a username. Use it to verify sellers or analyze marketplace activity.
Get eBay seller profile. Returns normalized details for a public eBay seller profile.
| Name | Required | Description | Default |
|---|---|---|---|
| seller | Yes | eBay seller username |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description only states it is a read operation ('get', 'returns'). No disclosure of rate limits, authentication needs, or data freshness.
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?
Two short sentences, no unnecessary words. Could potentially combine, but it is efficient.
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?
The description is adequate for a simple one-parameter tool, but without an output schema, it would benefit from specifying what 'normalized details' include (e.g., seller name, feedback score).
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% with a clear parameter description ('eBay seller username'). The tool description does not add extra meaning beyond the schema.
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 clearly states it gets an eBay seller profile and returns normalized details. It is specific but does not explicitly distinguish from sibling tools like ebay_seller_about or ebay_seller_feedback.
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?
No guidance on when to use this tool versus alternatives such as ebay_seller_about, ebay_seller_feedback, or ebay_seller_shop.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.