Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticslive_shop_shows

Fetch a Fanatics Live shop's own live, upcoming, or replay show list by slug and status; use status=replay for COMPLETE-status shows that cross-shop browse omits.

Instructions

Get a Fanatics Live shop's own live or replay show list. Returns a Fanatics Live shop's own live/upcoming or past/replay show list -- distinct from /fanaticslive/browse, which lists shows across all shops filtered by league. status=replay is the only way to observe a COMPLETE-status show.

Input Schema

NameRequiredDescriptionDefault
slugYesFanatics Live shop slug, e.g. from a shops-list result's slug field
afterNoPagination cursor from a previous response's next_cursor
limitNoMax shows to return (default 24)
statusYesWhich show list to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully reveals that status=replay is the only path to COMPLETE-status shows and clarifies the live/upcoming versus past/replay split, though it does not describe auth, rate limits, or ordering.

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?

The description is short and front-loads the core purpose. The first two sentences partially repeat the same idea, but the remaining content adds the sibling distinction and status nuance without excessive length.

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?

For a read-only list tool with full schema coverage and no output schema, the description is largely complete: it states what list is returned and how it differs from a sibling. It could do slightly more to explain pagination or return shape, but the schema already covers the pagination parameters.

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 description coverage is 100%, so the baseline is 3 even without extra parameter detail. The description goes further by explaining that status=replay is the only way to observe COMPLETE-status shows, adding meaning beyond the enum description alone.

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: getting a Fanatics Live shop's own live or replay show list. It also distinguishes this tool from /fanaticslive/browse, which covers shows across all shops filtered by league, so an agent can identify when this is the right tool.

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?

The description explicitly contrasts this tool with /fanaticslive/browse and explains that status=replay is the only way to observe a COMPLETE-status show. It provides clear context for choosing between status values, though it does not mention other nearby siblings such as individual show detail tools.

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