Fetch a Fanatics Live shop's public profile from its slug to get description, social links, follower count, channels, and staffers.
Get a Fanatics Live shop's public profile. Returns a Fanatics Live shop's public profile page: description, social links, follower count, and its channels and staffers.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Fanatics Live shop slug, e.g. from a shops-list result's slug field |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It discloses that the profile is public and read-only in effect, and enumerates the returned fields, but says nothing about auth requirements, rate limits, or whether missing shops return an error versus empty data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the action. The second sentence partly restates 'public profile' before listing fields, a minor redundancy, but nothing extraneous.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description usefully enumerates the return payload (description, social links, followers, channels, staffers), which is the key missing structured information. Sufficient for a simple single-param lookup.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the single slug parameter is already documented with format and provenance. The description adds no parameter-level detail beyond that baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Get a Fanatics Live shop's public profile') and enumerates the returned content. It is distinguishable from fanaticslive_shops and fanaticslive_shop_shows by resource granularity, though it never explicitly contrasts them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not guidance versus fanaticslive_shops (list) or fanaticslive_shop_shows. The only routing hint is indirect, in the schema description ('from a shops-list result's slug field'), which implies you first call a shops list, but the description itself says nothing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.