Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_live_streams_batch

Retrieve summaries for multiple eBay Live streams in one call by passing up to 9 stream IDs, returning titles, states, watch counts, hosts, tags, and preview media.

Instructions

Get multiple eBay Live streams. Returns summaries for several eBay Live streams in one call. ids is required and takes up to 9 stream ids, comma-separated or repeated. Each stream has its title, state, watch count, hosts, tags and preview media, without the per-host feedback summary. Ids that do not resolve are silently omitted, and the order may differ from the request.

Input Schema

NameRequiredDescriptionDefault
idsYesOne or more eBay Live stream/event ids, up to 9. Comma-separated or repeated query values are both accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose genuinely useful behavior: the returned field set, that the per-host feedback summary is excluded, that unresolvable ids are silently omitted, and that result order may differ from the request. It omits auth/permission and rate-limit context, but the silent-drop and ordering disclosures are exactly the kind of edge-case behavior an agent needs.

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

Conciseness4/5

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

Four sentences, each carrying distinct information (purpose, batch scope, parameter constraint, return shape, edge cases), and the core purpose is front-loaded. Slight redundancy between 'Get multiple' and 'Returns summaries for several' keeps it from a 5.

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

Completeness4/5

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

For a single-parameter tool with no output schema and no annotations, the description is close to complete: it covers input constraints, the fields returned, and two important edge cases (silent omission, non-deterministic order). Only the absence of error/auth behavior keeps it short of a 5.

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% for the single `ids` parameter, whose schema description already covers the 'up to 9, comma-separated or repeated' semantics. The description restates this rather than adding new meaning, so the baseline 3 is appropriate.

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

Purpose4/5

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

It states a specific verb and resource ('Get multiple eBay Live streams') and clarifies the batch nature ('Returns summaries for several ... in one call'), which separates it from the singular ebay_live_stream sibling. It does not, however, explicitly name or contrast itself with the plural ebay_live_streams sibling, so differentiation is implicit rather than stated.

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

Usage Guidelines3/5

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

The batch framing ('in one call', 'up to 9 stream ids') implies you should reach for this when you already hold multiple ids, but there is no explicit when-to-use or when-not-to-use guidance and no mention of the related single-stream or list tools. Usage is inferred rather than directed.

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