Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitch_user_clips

Retrieve a Twitch channel's public clips page by page using cursor-based pagination.

Instructions

twitch: Channel clips. GET /v1/twitch/user/clips. One page of a channel's public clips. An empty page costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when clips is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "handle": "<handle>"
    },
    "name": "twitch_user_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor from the previous page.
handleYesChannel login.
cache_max_ageNoServe a cached response when it is newer than this. A cache hit costs 0 credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 disclosure burden, and it does spend most of its text on the credit/cost model, including that empty pages, errors, and cache hits are free — genuinely useful behavioral context. However, it says nothing about auth requirements, rate limits, or what a returned page contains, and the cost rules are stated redundantly enough to be mildly confusing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded correctly, but four successive sentences restate the same pricing idea (empty page free, success costs 1, empty clips free, not-found charged per published cost), which is repetitive and partly overlapping. The route string adds little for an agent that already has the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Cost behavior is covered thoroughly, which fits a credit-metered API, but with no output schema the description should say what a page of clips looks like and how to detect the end of pagination. It is adequate but leaves the agent guessing about return shape and terminal-page behavior.

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 handle, cursor, and cache_max_age are already documented in the schema. The description adds no extra meaning about parameter formats or interactions beyond restating that a cache hit costs nothing, so 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: 'One page of a channel's public clips,' plus the underlying route GET /v1/twitch/user/clips. It does not explicitly distinguish itself from the sibling twitch_clip (single-clip lookup), so differentiation is left to inference from the parameter names.

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 only implied by the phrase 'one page of a channel's public clips' and the cursor parameter's schema text; the description never says when to choose this over twitch_clip or twitch_user_videos, nor any prerequisites. The cost rules give a reason to care about empty pages but no guidance on alternatives.

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