Skip to main content
Glama

captapi

by io.github.CDCStream
OverviewDiscussionsAdmin

twitch_user_videos

Twitch channel VODs — lean rows, video-id cursor, filter/sort, top-level broadcaster{} (flat 2). Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesTwitch channel URL or username, e.g. https://www.twitch.tv/shroud. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 20, max 100). Flat 2 credits per call. Hard ceiling: first 100 matching videos only — deeper history is not available (windowMax=100).
cursorNoPagination cursor = last video id from the previous nextCursor. Leave empty for the first page. Pages the first 100 matching videos only (not a raw offset).
sortByNoTIME (default, newest first) or VIEWS.
filterByNoARCHIVE | HIGHLIGHT | UPLOAD. Omit for all types — there is no default filter (unset filterBy is omitted, not null).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  2. Changed6 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor. Leave empty for the first page; then pass nextCursor from the previous response."New value: +"Pagination cursor = last video id from the previous nextCursor. Leave empty for the first page. Pages the first 100 matching videos only (not a raw offset)."
    • changedInput schema / properties / filterBy / description
      Previous value: -"ARCHIVE | HIGHLIGHT | UPLOAD. Omit for all types."New value: +"ARCHIVE | HIGHLIGHT | UPLOAD. Omit for all types — there is no default filter (unset filterBy is omitted, not null)."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 100. Flat 2 credits per call."New value: +"Max items to return (default 20, max 100). Flat 2 credits per call. Hard ceiling: first 100 matching videos only — deeper history is not available (windowMax=100)."
    • changedInput schema / properties / sortBy / description
      Previous value: -"TIME (default) or VIEWS."New value: +"TIME (default, newest first) or VIEWS."
    • changedInput schema / properties / url / description
      Previous value: -"Twitch channel URL or username, e.g. https://www.twitch.tv/shroud. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."New value: +"Twitch channel URL or username, e.g. https://www.twitch.tv/shroud. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."
  3. Changed4 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Pagination cursor. Leave empty for the first page; then pass nextCursor from the previous response.",
+  "type": "string"
+}
    • addedInput schema / properties / filterBy
      Added value: +{
+  "description": "ARCHIVE | HIGHLIGHT | UPLOAD. Omit for all types.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 30. Billed per result."New value: +"Max items to return. Default 20, max 100. Flat 2 credits per call."
    • addedInput schema / properties / sortBy
      Added value: +{
+  "description": "TIME (default) or VIEWS.",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 30. Flat 2 credits on native success."New value: +"Max items to return. Default 20, max 30. Billed per result."
  5. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 30. Billed per result."New value: +"Max items to return. Default 20, max 30. Flat 2 credits on native success."
  6. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  7. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
+  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
+  "type": "boolean"
+}
  8. Added

TDQS

A4/5.0
Behavior5/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 so well: it discloses credit costs, free cache hits, no charge for empty/failed results, default fresh behavior, pagination style, and row shape. It also signals that this is a read-style listing operation without destructive side effects. This is substantial behavioral context beyond the schema.

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

Conciseness5/5

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

The description is compact and information-dense, with the most important facts front-loaded. Every clause provides useful operational information, and there is no filler or redundant restating of the tool name. The two-sentence structure is easy for an agent to parse.

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?

Given the rich input schema and lack of an output schema, the description covers the main operational concerns: scope, pagination, filtering, sorting, cost, caching, and failure behavior. It does not detail response fields beyond 'lean rows' and the broadcaster object shape, but this is sufficient for an agent to select and invoke the tool. A little more explicit output-structure guidance would make it fully complete.

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%, and each parameter already has detailed descriptions, so the baseline is 3. The description adds some related context ('video-id cursor, filter/sort, top-level broadcaster{}') but mostly restates or hints at what the schema already documents. It does not meaningfully compensate for any missing parameter-level semantics.

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 clearly identifies the resource as 'Twitch channel VODs' and conveys that this endpoint returns video rows with filtering and sorting. It does not use an explicit verb like 'list' or 'fetch', but the 'lean rows, video-id cursor, filter/sort' phrasing makes the operation unambiguous. The name plus 'Twitch channel VODs' differentiates it from sibling tools like twitch_clip and twitch_user_schedule.

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?

The resource statement 'Twitch channel VODs' implies when to use this tool, and the schema warns against cross-platform URLs. However, the description does not explicitly state when to use this tool instead of related Twitch siblings or other channel-video tools. The guidance is mostly inferred from the resource name rather than stated.

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

All captapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources