Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitch_clip

Fetch details for a Twitch clip URL to inspect clip metadata and credit usage without parsing API envelopes.

Instructions

twitch: Clip. GET /v1/twitch/clip. Get Twitch clip details (1 credit). The answer is a bare JSON array with no envelope; the fetchproof-credits-charged and fetchproof-credits-remaining headers carry the credits. 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": {
      "url": "<url>"
    },
    "name": "twitch_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTwitch clip URL
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses the credit price, that failures/blocked/timeout/invalid/cache-hit requests are free, that the response is a bare JSON array with no envelope, and that credit counts arrive in response headers. It omits auth requirements and rate limits, which keeps it short of a 5.

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?

Front-loaded with the endpoint and purpose, which is good, but the billing content is redundant — '(1 credit)' is restated by 'Costs 1 credit when it succeeds.' The final sentence about not-found/empty results is circular ('charged only where that operation's published cost says so') and adds little.

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 two-parameter read tool with no output schema, the description covers the important unknowns: the return shape (bare JSON array), where credit metadata lives (headers), and the full cost model. Only authentication expectations are left unstated.

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%, including an example URL and an explanation of cache_max_age, so the schema does the heavy lifting. The description only indirectly illuminates cache_max_age via the 'cache hits cost nothing' sentence and adds no format or constraint detail beyond the schema.

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 Twitch clip details') and pins it to the endpoint GET /v1/twitch/clip, so it is clearly a single-clip lookup rather than a listing. It does not explicitly contrast with siblings like twitch_user_clips, but the resource granularity is unambiguous from the name and description together.

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 explicit guidance on when to choose this over twitch_user_clips or twitch_profile, and no stated prerequisites such as auth or URL format requirements. Usage is only implied by the required url parameter. The cost sentences describe billing outcomes, not tool-selection conditions.

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