Retrieve normalized summaries for up to 9 eBay Live streams in a single request. Accepts comma-separated or repeated IDs for batch processing.
Get multiple eBay Live streams. Returns normalized summaries for multiple eBay Live streams/events in one call, up to 9 ids per request.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | One or more eBay Live stream/event ids, up to 9. Comma-separated or repeated query values are both accepted. |
Changes observed during successful MCP inspections.
v1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It discloses that the return value is a 'normalized summaries' batch, and imposes a 9-id capacity. However, it does not mention behavior for invalid IDs, partial errors, or the exact shape/structure of the summaries.
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 concise sentences with no filler. The main purpose and the batch cap are front-loaded, and every sentence contributes.
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 batch-read tool, the description is largely sufficient: it states the ids parameter, the limits, and the type of return ('normalized summaries'). Without an output schema or annotations, it could say more about the summary shape, but it is close to complete for calling correctness.
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 description coverage is 100%, and the schema already explains the comma-separated or repeated-query format and the 9-id limit. The description repeats the cap but adds no substantial 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 a specific verb ('Get') and resource ('multiple eBay Live streams'), and spells out the batch nature with 'in one call, up to 9 ids per request'. This strongly distinguishes it from singular tools like ebay_live_stream or listing tools like ebay_live_streams.
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 intended use case is implied: when you need multiple eBay Live stream/event ids fetched in one batch. However, the description never names alternatives or states when not to use it, such as single ID retrieval via ebay_live_stream or listing via ebay_live_streams.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.