Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_live_stream

Retrieve a single eBay Live stream or event by id to get its title, state, schedule, viewer and engagement counts, host ratings, and live, preview, and replay URLs.

Instructions

Get an eBay Live stream. Returns one eBay Live stream or event by id, taken from the streams[].id of the stream list. The response has title, description, state, start and end times, viewer, watch and like counts, tags, channels and the live, preview and replay URLs. Each host carries a 365-day feedback summary and four average ratings. An unknown id returns 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYeseBay Live stream/event id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.9/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 so well: it enumerates the returned fields (state, times, counts, URLs), describes host feedback summaries and the 365-day window, and discloses error behavior (unknown id returns 404). It omits only explicit confirmation that this is a non-mutating read and any rate/pagination notes.

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?

Front-loaded with the core action, then the return contents and error case. It is a bit enumerative in the middle, but every clause conveys selection-relevant information rather than padding.

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?

No output schema and no annotations, so the description must explain both return shape and failure mode; it does both thoroughly (fields, host ratings, 404 on unknown id). Nothing essential for calling it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real value by telling the agent where the required id comes from (streams[].id of the stream list), which the schema's 'eBay Live stream/event id' does not convey.

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?

States a specific verb (Get) and resource (eBay Live stream/event) and clarifies it returns a single entity by id. It even explains the id provenance (streams[].id from the stream list), which implicitly points at the sibling list tool. It stops short of explicitly naming siblings like ebay_live_streams_batch or ebay_live_stream_items.

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?

Usage is implied: the agent learns the id comes from the stream list, which signals the fetch-vs-list workflow. However there is no explicit when-to-use/when-not or named alternative, so the routing guidance remains inferential 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