Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_live_streams

Fetch currently live and upcoming eBay Live streams by category channel, using session IDs and request numbers to page through results.

Instructions

List eBay Live streams. Returns currently live and upcoming eBay Live streams for a category channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoeBay Live category channel, defaults to explore
session_idNoPagination session id from a previous response's session_id
request_numberNoPagination cursor from a previous response's next_request_number, defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  "explore",
+  "IPqZx79LNuwFcSVt",
+  "oHjQFTlZ5cYgWkjB",
+  "l68DJtBAVZge4x4n",
+  "2Nk3OYiOJHfXqpWG",
+  "5quuEnjO3axyz46U",
+  "nGpMTpm13Q86Eaoo",
+  "sYRxeaskGmNC6xaB",
+  "iYaYo88zN2vtQorh",
+  "GYAbsFw6onSNloAb",
+  "WJ9zLwYjK8njaBtN",
+  "rALkRyk8gXHzIBR6",
+  "DNta0sJ8Y6NXZsC9",
+  "GU4UfBzZSF4jiteS",
+  "IO7Oih07PtNJSWhU",
+  "cF4xtF8z9riubmLh",
+  "bywKDIdtxhi4hUSO"
+]
  2. Addedv1.14.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns both live and upcoming streams and that it is scoped to a category channel, which is useful. However, it doesn't mention pagination behavior, response format, or any rate limits or side effects. For a read-only listing tool, this is adequate but not rich.

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?

Two sentences with no filler. The core action and scope are front-loaded. It could be slightly more informative about pagination, but it is appropriately concise.

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

Completeness3/5

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

For a simple listing tool with no required parameters and full schema coverage, the description is mostly complete. However, it lacks any mention of pagination semantics (session_id, request_number) in the description, and there is no output schema to clarify the return shape. The sibling ebay_live_streams_batch suggests a batch variant exists, but the description doesn't clarify the relationship.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds no additional meaning beyond the schema, but the baseline of 3 applies because the schema does the heavy lifting. The description's mention of 'category channel' aligns with the category parameter but adds no new detail.

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?

The description states a specific verb ('List') and resource ('eBay Live streams'), and clarifies the scope by noting it returns 'currently live and upcoming' streams for a category channel. It doesn't explicitly differentiate from the sibling ebay_live_streams_batch or ebay_live_stream, but the basic purpose is clear.

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 description implies usage for listing live/upcoming streams by category channel, but it doesn't explicitly state when to use this tool versus alternatives like ebay_live_streams_batch or ebay_live_stream. No exclusions or alternative routing are provided.

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