Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

twitch_vod_comments

Fetch a page of chat replay messages from a Twitch VOD at a chosen timestamp, then paginate forward using the last comment's offset in seconds.

Instructions

Get a Twitch VOD's chat replay. Returns one page of a Twitch VOD's chat replay (past-broadcast chat messages), starting at a given point in the video's timeline. Paginate forward by re-requesting with the last returned comment's offset_seconds.

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)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.14.0Aug 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and usefully discloses that it returns one page and how pagination works. However, it omits auth requirements, rate limits, and any indication of page size or ordering beyond the offset mechanics.

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?

Three tight sentences, front-loaded with the purpose, then return shape, then pagination. Every sentence earns its place with no redundancy.

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 paginated read tool with full schema coverage and no output schema, the description covers purpose, return granularity, and pagination adequately. It could add auth/rate-limit context but nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds value by explaining how offset is used (start point in the timeline) and linking pagination to the returned offset_seconds. This is real semantic guidance beyond the field definitions.

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 (Get) and resource (a Twitch VOD's chat replay), and clarifies it is past-broadcast chat rather than live chat. This clearly distinguishes it from siblings like twitch_videos and twitch_streams without needing to open a schema.

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

Usage Guidelines4/5

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

Gives clear operational guidance for pagination (re-request with the last returned comment's offset_seconds) and the starting-point semantics. It does not name alternatives or state when NOT to use it, but the usage context is unambiguous.

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

Deploy Server