Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitch_user_videos

Fetch a Twitch user's videos by handle with optional sorting and filtering to support channel content research and monitoring.

Instructions

twitch: User Videos. GET /v1/twitch/user/videos. Get Twitch user videos Costs 1 credit when it succeeds. 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_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesTwitch handle
sort_byNoSort by
filter_byNoFilter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose a genuinely useful behavioral trait — the credit-charging model, including that failures, blocks, timeouts, invalid requests and cache hits are free — which is real value beyond the schema. It says nothing about authentication, pagination, or the shape of the returned list, so significant behavioral gaps remain.

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

Conciseness3/5

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

The purpose is front-loaded, but the opening three fragments ("twitch: User Videos. GET /v1/twitch/user/videos. Get Twitch user videos") say the same thing three times. The pricing sentences are informative but verbose boilerplate that occupies more space than the functional description.

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?

For a simple three-parameter list endpoint with no output schema and no annotations, the definition covers purpose and cost but omits return format, pagination/cursor behavior, and acceptable values for the two optional filters. An agent could call it, but would do so guessing at the semantics of sort_by and filter_by.

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 the baseline is 3. The description adds no meaning beyond the schema for handle, sort_by or filter_by — in particular it does not clarify the accepted values for sort_by (VIEWS) or filter_by (ARCHIVE), which the schema only hints at via examples rather than enums.

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?

The description states a specific verb and resource ("Get Twitch user videos") and pins it to an endpoint (GET /v1/twitch/user/videos), so an agent knows exactly what it retrieves. It does not, however, distinguish itself from near siblings such as twitch_user_clips or twitch_user_schedule, leaving the boundary to be inferred from the name alone.

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?

There is no statement of when to use this tool versus alternatives (e.g. clips vs videos), no prerequisites, and no exclusions. The only conditional language concerns billing, not selection, so the agent gets no routing guidance.

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