Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_live_streams

List live and upcoming eBay Live streams by category channel, with titles, states, start times, watch counts, hosts, tags, and preview media. Paginate using request_number and session_id.

Instructions

List eBay Live streams. Lists live and upcoming eBay Live streams for one category channel, set with category (default explore; other values are channel ids such as IPqZx79LNuwFcSVt for Sports Singles). Each stream has its title, state, start time, watch count, hosts, tags and preview media. Host feedback is not included. Page on with next_request_number and session_id, passed back as request_number and session_id.

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

A4.1/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 reasonably well: it enumerates returned fields (title, state, start time, watch count, hosts, tags, preview media), explicitly states an exclusion ('Host feedback is not included'), and describes pagination mechanics. It omits auth requirements and rate limits, so it is not fully complete.

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 progressively adds scope, return fields, and pagination. Minor redundancy between 'List eBay Live streams' and the following 'Lists live and upcoming eBay Live streams,' but overall tight and well-ordered.

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?

No output schema and no annotations exist, so the description must cover return shape and behavior, which it largely does by naming returned fields and the excluded host feedback. Pagination is covered, leaving only auth/rate-limit context unaddressed.

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 baseline is 3, but the description adds real value beyond the schema: it explains the default category, maps the opaque enum id `IPqZx79LNuwFcSVt` to 'Sports Singles', and clarifies the pagination round-trip between next_request_number/session_id and request_number/session_id.

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?

The description states a specific verb and resource ('List eBay Live streams') and immediately narrows scope to 'live and upcoming eBay Live streams for one category channel.' This clearly distinguishes the plural listing tool from siblings like ebay_live_stream (singular detail) and 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 by the scoping ('for one category channel'), but there is no explicit when-to-use, when-not-to-use, or alternative routing against ebay_live_stream or ebay_live_streams_batch. An agent can infer intent but receives no exclusions or prerequisite guidance.

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