Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

twitch_channel

Retrieve a Twitch channel's profile and live status by login, returning partner status, team, last broadcast title, and live start time and game.

Instructions

Get a Twitch channel's profile and live status. Returns a Twitch channel's profile (partner status, team, last broadcast title) plus its current live status (started time and game/category, when live).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesTwitch channel login (the lowercase URL slug, e.g. caedrel for twitch.tv/caedrel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the response contents (partner status, team, last broadcast title, live started time, game/category). However it is silent on behavioral edge cases an agent needs: what happens when the channel is offline, invalid, or not found, and whether any auth is required.

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?

Two short sentences, front-loaded with the core action. There is mild redundancy in restating 'profile and live status' twice, but nothing is bloated.

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 one-parameter lookup with no output schema and no annotations, the description usefully enumerates the returned fields, which compensates for the missing output schema. Only the offline/error behavior is left unaddressed, a minor gap at this complexity level.

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?

Schema coverage is 100% and the login parameter already includes a clear format explanation and example (lowercase URL slug). The description adds nothing beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 Twitch channel's profile and live status. An agent can tell it retrieves a single channel's data, but it never distinguishes itself from near-siblings like twitch_streams or twitch_search, so the reader must infer the boundary themselves.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives. The description never says to use this for a single known login versus twitch_streams for a list of live channels or twitch_search for discovery, leaving the agent to guess.

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