Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Twitch profile videos

twitch_profile_videos_list
Read-onlyIdempotent

Retrieve a list of videos from a Twitch channel by handle, optionally filtered by type and sorted by time or views.

Instructions

List videos from a Twitch channel by handle. Requires handle. Returns a list.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitch_profile_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Twitch handle to look up, with or without a leading @.
sortByNoOptional sort order.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
filterByNoOptional filter for the type of Twitch videos to return. `archive`: full unedited past broadcasts (VODs). `highlight`: shorter clips curated/edited by the streamer from past broadcasts. `upload`: videos uploaded directly, not recorded from a live stream.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description contributes only 'Returns a list', saying nothing about pagination, result caps, ordering defaults, or how the optional filters change output — little value beyond structured fields.

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?

Three short, front-loaded sentences with no bloat. The final sentence 'Returns a list' is largely redundant filler, keeping it out of the top band.

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?

This is a simple list tool with a fully documented schema and rich annotations, so most of the burden is carried elsewhere. However, with no output schema the agent still lacks any signal about pagination, result limits, or ordering defaults, which the description could cheaply have supplied.

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 every parameter (handle, sortBy, filterBy, context, llm_model, conversation_id) is already documented in the schema, including the enum meanings. The description only echoes the handle requirement, adding nothing beyond the schema; 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?

The description states a specific verb and resource ('List videos from a Twitch channel') and scopes it to a handle, which is enough to separate it from twitch_profile_get or twitch_clip_get. It stops short of naming or contrasting any sibling tool explicitly.

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?

'Requires `handle`' is a prerequisite restatement, not usage guidance. The description never says when to pick this tool over twitch_profile_get or twitch_clip_get, nor when to apply filterBy/sortBy versus leaving them unset.

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