Crawlora MCP

twitch_channel

Read-only

Fetch a Twitch channel profile and current live status, including partner/team and broadcast title. Use twitch_search to discover channels, twitch_streams for live details, or twitch_team for roster information.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "login": "<login>"
    },
    "name": "twitch_channel"
  }
}

Input Schema

Name	Required	Description	Default
`login`	Yes	Twitch channel login (the lowercase URL slug, e.g. caedrel for twitch.tv/caedrel)

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / login / description

Added value: +"Twitch channel login (the lowercase URL slug, e.g. caedrel for twitch.tv/caedrel)"

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful scope context beyond that: this call returns a composite of profile plus live status (partner/team, broadcast title), which helps an agent understand it is not just a static profile lookup.

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?

Two sentences, zero waste. The core capability is front-loaded and the sibling routing follows it; nothing is padded or 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?

With an output schema present, return values need not be explained, and the description covers purpose plus alternatives adequately. It is complete for correct invocation, with only minor room to note auth or rate-limit caveats.

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 single login parameter is fully documented with a slug example, so the schema does the work. The description adds no parameter-level syntax or format detail, which is the expected baseline when the schema is complete.

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 (Fetch) and resource (Twitch channel profile + current live status) and enumerates the payload (partner/team, broadcast title). It is clearly distinguishable from siblings like twitch_streams and twitch_team without opening any schema.

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?

Explicitly routes the agent: twitch_search to discover channels, twitch_streams for live details, twitch_team for roster. This tells the agent both when to use this tool and which alternative covers adjacent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?