Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

twitch_videos

Retrieve a Twitch channel's past broadcast VODs ranked by view count, including title, views, length, date, and game. Specify the channel login to fetch up to 100 videos.

Instructions

Get a Twitch channel's videos (VODs). Returns a Twitch channel's past-broadcast videos (VODs), ranked by view count: title, view count, length, publish date, and the game it was recorded under.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of videos to return (default 20, max 100)
loginYesTwitch channel login (the lowercase URL slug, e.g. lck for twitch.tv/lck)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that results are ranked by view count and lists the returned fields, but says nothing about permissions, pagination behavior, or defaults beyond the schema's 20/100 limit note.

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?

Two front-loaded sentences with no filler, leading with the action and following with return details. Minor redundancy in restating 'past-broadcast videos (VODs)' after already saying videos.

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 simple 2-parameter retrieval tool with no output schema, the description supplies the return fields and ordering, which compensates for the absent output schema. It is complete enough to call correctly, missing only usage routing and pagination notes.

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 (login, limit) are already documented in the schema; the description adds no syntax or format meaning beyond that. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Get a Twitch channel's videos (VODs)') and clarifies these are past-broadcast videos, which implicitly separates it from live-stream siblings like twitch_streams. It never names a sibling explicitly, so the differentiation is left to inference.

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 purpose (fetch a channel's VODs) but there is no explicit when-to-use, when-not-to-use, or alternative routing (e.g. twitch_clips vs twitch_videos vs twitch_streams). Nothing misleading, but guidance is left to inference.

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