Retrieve normalized eBay Live stream details by ID, including each host's feedback summary for the last 365 days.
Get an eBay Live stream. Returns normalized detail for a single eBay Live stream/event, including each host's feedback summary for the last 365 days.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | eBay Live stream/event id |
Changes observed during successful MCP inspections.
v1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the burden. It adequately indicates the operation is a read/get action and mentions the output includes normalized detail and each host's feedback summary. Additional behavioral context (not found behavior, auth requirements, response format quirks) is missing, but for a simple single-resource lookup this is acceptable.
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 very compact: two sentences front-load the main action ('Get an eBay Live stream') and then specify what is returned. Every sentence adds meaningful detail without redundancy.
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 single-parameter lookup tool, the coverage is adequate in the sense of core functionality and returned data. But with no output schema, no siblings mention, and no usage boundaries, an agent might not know when to choose this over the closely related ebay_live_streams or ebay_live_streams_batch. Still, for such a minimal interface, the shortfalls are mild.
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?
The schema already fully documents the only parameter ('id') with description 'eBay Live stream/event id'. The tool description doesn't add semantic detail beyond this, but with 100% schema coverage, the baseline of 3 applies and no extra compensation is needed.
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 states a specific verb and resource: 'Get an eBay Live stream', and clarifies it returns normalized detail for a single stream/event including host feedback. This distinguishes it from list/batch siblings like ebay_live_streams and ebay_live_streams_batch, though it doesn't explicitly name them.
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 phrase 'single eBay Live stream/event' implies this tool is for retrieving one specific stream rather than listing all streams or batch fetching. However, there is no explicit when-to-use guidance, no mention of alternatives like ebay_live_streams, and no exclusions, leaving some inference up to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.