Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_live_stream_items

List featured items from an eBay Live stream by event ID, including listing details, price, bid count, auction status, leader, and winner usernames.

Instructions

List an eBay Live stream's featured items. Lists the items currently featured in an eBay Live stream, identified by the required event id. Each item has its listing id, title, price and currency, bid count, sale type, leader and winner usernames, and auction_status (READY, LIVE or ENDED). A stream with no featured items, or an unknown id, returns an empty items array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYeseBay Live stream/event id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden, and it does a solid job: it enumerates the returned fields (listing id, title, price/currency, bid count, sale type, leader/winner usernames, auction_status) and discloses the three auction_status values plus the empty-array edge case for unknown ids. It stops short of noting auth or rate-limit behavior, but the read-only nature is clear from 'List'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the purpose, followed by the identifying parameter and the return/edge-case details. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description compensates by describing the returned fields, the auction_status enum, and the empty-result behavior — everything an agent needs to call it and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single parameter, so the schema already documents `id`. The description reinforces that `id` is required and refers to the event/stream id, matching the schema, but adds no syntax or format detail beyond it — baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (featured items of an eBay Live stream), and immediately names the identifying key (`id`). An agent can distinguish it from the sibling ebay_live_stream / ebay_live_streams tools that operate on streams themselves rather than their featured items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context: it requires an event `id` and returns an empty `items` array when there are no featured items or the id is unknown, which tells the agent not to treat an empty result as an error. It does not explicitly compare against sibling tools like ebay_live_stream or ebay_live_streams_batch, so routing is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools