Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticslive_channel

Retrieve a Fanatics Live channel's details, including its parent shop and initial list of live, upcoming, and past shows. Use to access channel-specific show data from public Fanatics Live GraphQL API.

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. Public data sourced from Fanatics Live's own GraphQL API.

Input Schema

TableJSON 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.5/5.0
Behavior4/5

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

Although there are no annotations, the description discloses that the data is public and sourced from Fanatics Live's GraphQL API, implying a safe read operation. It also notes the return is limited to the first page of shows, alerting the user to pagination limitations. It doesn't contradict any annotations since none exist.

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?

The description is three sentences, each carrying essential information: purpose, response content, and routing to sibling tools. No redundant phrasing or fluff; it's front-loaded with the core action.

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?

For a single-parameter read tool with no output schema, the description adequately explains what is returned (parent shop, first page of shows), mentions data source and public nature, and directs users to alternative endpoints for fuller data. Nothing critical is missing for an agent to decide and call this tool correctly.

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?

The schema already fully describes the id parameter (a UUID, e.g., from a shop or show result's channel.id field) with 100% coverage. The description adds no further meaning about the parameter beyond what the schema provides, so the baseline 3 is appropriate.

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 specifies the exact operation: getting a Fanatics Live channel's detail page. It enumerates the returned content (parent shop, first page of live/upcoming and past/replay shows) and distinguishes it from sibling tools like /fanaticslive/shop and /fanaticslive/shop/{slug}/shows, making it unmistakable.

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

Usage Guidelines5/5

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

It explicitly points to alternatives: /fanaticslive/shop/{slug} for a shop's full channel list and /fanaticslive/shop/{slug}/shows for cursor-paginated full show history. This tells an agent precisely when to use this tool versus those, and clarifies the scope of this tool (only first page).

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