Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

twitch_schedule

Retrieve a Twitch channel's upcoming broadcast schedule with titles, times, and categories for the next 1-4 weeks. Returns empty list if none.

Instructions

Get a Twitch channel's broadcast schedule. Returns a Twitch channel's upcoming broadcast schedule -- planned segments with title, start/end time, and game/category -- starting today. A channel with no schedule configured returns an empty segments list, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weeksNoNumber of weeks ahead to return, starting today (default 1, max 4)
channelYesTwitch channel login (the lowercase URL slug)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the return shape (planned segments with title, times, category) plus a real edge case: a channel with no schedule returns an empty list, not an error. It omits auth/permission requirements and any rate-limit or pagination behavior, but the empty-result disclosure is meaningful added context.

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?

Three short sentences, front-loaded with the core purpose and ending on the most surprising behavioral detail (empty list over error). There is mild redundancy between the first two sentences ('Get ... broadcast schedule' / 'Returns ... upcoming broadcast schedule'), costing it a point.

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 two-parameter read tool with no annotations and no output schema, the description covers purpose, return contents, and the empty-result edge case, which is what an agent needs. It would be a 5 with a note on required channel identifier validity or the weeks default, but nothing critical is missing.

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 the channel slug and the max-4 weeks-ahead parameter are already documented in the schema with defaults and bounds. The description's 'starting today' phrase reinforces the weeks semantics but adds no syntax or format detail 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 + resource ('Get a Twitch channel's broadcast schedule') and elaborates on what the payload contains (segments with title, start/end time, game/category). It is clearly distinguishable from live-view siblings like twitch_streams by implication, though it never names an alternative to route the agent explicitly.

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

Usage Guidelines3/5

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

The 'starting today' / 'upcoming' framing tells the agent when the tool is temporally applicable, and the empty-list note hints at validation behavior. However, there is no explicit when-to-use vs sibling guidance (e.g., versus twitch_channel or twitch_streams), so usage is only implied.

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