Crawlora MCP

twitch_schedule

Read-only

Fetch a Twitch channel's planned broadcast segments starting today; an unset schedule returns an empty list. Use twitch_streams for a current live broadcast or twitch_channel for channel profile and live status.

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": {
      "channel": "<channel>"
    },
    "name": "twitch_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`weeks`	No	Number of weeks ahead to return, starting today (default 1, max 4)
`channel`	Yes	Twitch channel login (the lowercase URL slug)

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.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / channel / description

Added value: +"Twitch channel login (the lowercase URL slug)"

addedInput schema / properties / weeks / description

Added value: +"Number of weeks ahead to return, starting today (default 1, max 4)"

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context not in the annotations: an unset schedule returns an empty list rather than erroring. It stops short of describing pagination or result ordering, keeping it just below the top mark.

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 tightly written sentences with the core action front-loaded and the routing guidance second. Every clause earns its place: action, edge-case behavior, and sibling disambiguation, with no filler.

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?

An output schema exists, so return values needn't be explained. The description covers scope, the empty-result edge case, and sibling routing, which is everything an agent needs to select and invoke 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?

Schema coverage is 100%, so both parameters (channel, weeks) are already fully documented in the schema. The phrase 'starting today' reinforces the weeks semantics but adds no format, bounds, or lookup detail beyond the structured field descriptions, so baseline 3 applies.

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 and resource ('Fetch a Twitch channel's planned broadcast segments') with clear temporal scope ('starting today'). It explicitly names the two sibling tools it is not (twitch_streams, twitch_channel), so an agent can route 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?

Gives explicit when-to-use guidance by naming alternatives and the condition that selects each: twitch_streams for a current live broadcast, twitch_channel for profile and live status. This is a textbook routing instruction with no inference required.

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?