Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticslive_channel

Retrieve a Fanatics Live channel detail page, including its parent shop and first pages of live, upcoming, and past or replay shows. Use the channel UUID to inspect one channel's schedule and history.

Instructions

Get a Fanatics Live channel's detail page. Returns a Fanatics Live channel's own detail page: its parent shop, and a first page of its live/upcoming and past/replay shows. A shop can run several channels (e.g. a league-specific sub-feed) -- see /fanaticslive/shop/{slug} for a shop's full channel list and /fanaticslive/shop/{slug}/shows for cursor-paginated access to a full show history.

Input Schema

NameRequiredDescriptionDefault
idYesFanatics Live channel id (a UUID), e.g. from a shop or show result's channel.id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the load well: it discloses that only a 'first page' of live/upcoming and past/replay shows is returned and that a cursor-paginated alternative exists for full history. It doesn't mention auth or rate limits, but for a read-only detail call the key behavioral constraint (truncated results) is surfaced.

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, then return contents, then sibling routing. Every sentence conveys information the agent needs; nothing is redundant.

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 exists, but the description adequately explains what the call returns (parent shop and first page of shows). The primary gaps—auth expectations and exact pagination semantics—are minor for a simple read tool, and the truncation limit is already noted.

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?

Only one parameter, and schema coverage is 100% with a clear description including format (UUID) and provenance ('from a shop or show result's channel.id field'). The description adds no parameter detail beyond the schema, so the baseline of 3 applies.

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 and resource ('Get a Fanatics Live channel's detail page') and immediately enumerates what is returned: parent shop plus a first page of live/upcoming and past/replay shows. It also distinguishes itself from fanaticslive_shop and fanaticslive_shop_shows by naming their distinct roles.

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?

Clearly signals this is for a single channel's detail and directs the agent to /fanaticslive/shop/{slug} for a full channel list and /fanaticslive/shop/{slug}/shows for full paginated history. The alternative routing is explicit, though there is no explicit 'do not use this when...' clause beyond the sibling pointers.

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