Retrieve normalized eBay seller about details—stats, top-rated status, location, member-since, and store categories—by username.
Get eBay seller about details. Returns normalized seller about information from the public eBay store about tab, including seller stats, top-rated status, optional location/member-since fields, and cleaned store categories.
| 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?
With no annotations, the description bears full burden. It states the tool 'gets' data, implying a read operation, and mentions 'normalized' and 'cleaned' output. However, it does not explicitly confirm non-destructive behavior, authentication needs, or rate limits.
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 a single sentence with a clear purpose and a list of return fields. It is front-loaded and concise, with zero wasted words.
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?
Given no output schema, the description covers return values well (stats, top-rated, location, categories). It is sufficient for a simple retrieval tool, though it could mention that the endpoint is public and requires no authentication.
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 single parameter 'seller' described as 'eBay seller username'. The tool description does not add additional semantic meaning beyond what the schema provides, 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 clearly states 'Get eBay seller about details' and specifies the source and content, including seller stats, top-rated status, location/member-since fields, and cleaned categories. This distinguishes it from sibling tools like ebay_seller, ebay_seller_feedback, and ebay_seller_shop.
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 seller about details are needed, but lacks explicit when-not-to-use or alternative suggestions among siblings. No guidance is provided for choosing between this and similar tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.