Crawlora MCP

twitch_vod_comments

Read-only

One page of a Twitch VOD's chat replay, starting at a given point in the video's timeline.

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": {
      "video": "<video>"
    },
    "name": "twitch_vod_comments"
  }
}

Input Schema

Name	Required	Description	Default
`video`	Yes	Twitch VOD/video id (the numeric id from twitch.tv/videos/{id})
`offset`	No	Start the page from this point in the VOD's timeline, in seconds (default 0)

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

Added value: +"Start the page from this point in the VOD's timeline, in seconds (default 0)"

addedInput schema / properties / video / description

Added value: +"Twitch VOD/video id (the numeric id from twitch.tv/videos/{id})"

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine context beyond that: the result is page-based ('one page'), and the content is a replayed chat log rather than live chat. It does not discuss rate limits or how to page forward, but with annotations present this is solid.

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?

A single tight sentence with the resource and the offset scoping front-loaded and zero wasted words.

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 a full output schema and annotations, the agent has what it needs; the description covers what the tool returns and the offset semantics. It stops short of explaining subsequent-page navigation, but that is largely return-value territory handled by the output schema.

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 the video id and the offset (seconds, default 0) are already fully documented. The description restates 'starting at a given point in the video's timeline' but adds no format or syntax 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 and resource: it retrieves one page of a Twitch VOD's chat replay. This clearly distinguishes it from siblings like twitch_videos or twitch_clips, which deal with video metadata rather than chat. It does not explicitly name a sibling, but the resource is unambiguous.

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?

Usage is implied by the description (call this to fetch chat replay comments for a VOD), but there is no explicit when-to-use/when-not statement, no prerequisites, and no mention of an alternative tool. Adequate but leaves the agent to infer the context.

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?