Crawlora MCP

twitch_videos

Read-only

Fetch a Twitch channel's past-broadcast VOD records ranked by views. Use twitch_clips for recent short highlights or twitch_streams for currently live content.

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_videos"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of videos to return (default 20, max 100)
`login`	Yes	Twitch channel login (the lowercase URL slug, e.g. lck for twitch.tv/lck)

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 / limit / description

Added value: +"Number of videos to return (default 20, max 100)"

addedInput schema / properties / login / description

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

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds useful ordering context ('ranked by views') but says nothing about pagination, result caps beyond the schema's limit, or how far back the VOD archive goes.

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 tight sentences with the core action and the disambiguation front-loaded ahead of the alternatives. No filler and nothing to trim.

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-format explanation is unnecessary, and annotations cover the safety profile, so the description is nearly complete. Only minor gaps remain around archive depth and pagination behavior for a tool with a max-100 limit.

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 description coverage is 100%, so both parameters (login format, limit default/max) are already fully documented. The description adds no parameter-level detail beyond what the schema provides, making the baseline 3 appropriate.

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 past-broadcast VOD records') plus a distinguishing sorting trait ('ranked by views'). It explicitly names the sibling tools it is not (twitch_clips, twitch_streams), 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 routing: twitch_clips for recent short highlights and twitch_streams for currently live content, implying this tool is for archived full VODs. The alternative conditions are stated rather than left to inference.

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?