Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

twitch_clips

Retrieve a Twitch channel's clips from the last 7 days, ranked by views, with title, view count, duration, curator, and game details.

Instructions

Get a Twitch channel's clips. Returns a Twitch channel's clips (last 7 days), most-viewed first: title, view count, duration, curator, and the game it was recorded under.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.14.0Aug 21, 2026

TDQS

B3.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 behavioral burden, and it does disclose two non-obvious traits: the 7-day recency window and the most-viewed-first sort order, plus the returned fields. However it omits auth/permission requirements and pagination behavior, which an agent would still want for a channel-scoped read.

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 short sentences with the key facts front-loaded. Minor redundancy between 'Get a Twitch channel's clips' and 'Returns a Twitch channel's clips', but no wasted sentences.

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 read tool with no output schema, listing the returned fields (title, view count, duration, curator, game) and the 7-day/most-viewed-first behavior makes it usable as-is. Pagination and rate/auth details are the only notable omissions.

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 login (lowercase URL slug) and limit (default 20, max 100) are already fully documented in the schema. The description adds no syntax or constraint detail beyond that, 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?

Specific verb ('Get') plus resource ('a Twitch channel's clips') with the scope of the returned data spelled out. It is clearly distinguishable from twitch_videos/twitch_vod_comments by resource, though it does not explicitly name or contrast with those siblings.

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

Usage Guidelines2/5

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

The description states what the tool returns but gives no when-to-use guidance, no prerequisites, and no mention of alternatives such as twitch_videos or twitch_vod_comments. Usage is only inferable from the name.

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

Deploy Server