Skip to main content
Glama

Twitch

by io.github.pipeworx-io

Get Streams

get_streams
Read-onlyIdempotent

Get live Twitch streams, optionally filtered by game name and/or language. Returns streamer name, title, current viewer count, and thumbnail for each live stream. Omit game for the overall top live streams across Twitch. Example: get_streams({ game: "Just Chatting", first: 20, language: "en" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameNoGame NAME to filter by (e.g. "Fortnite", "Just Chatting"). Resolved to a game id automatically.
firstNoNumber of streams to return (default 20, max 100)
_apiKeyNoOptional — your own Twitch credentials as CLIENT_ID:CLIENT_SECRET for higher limits; omit to use the shared Pipeworx key.
languageNoOptional ISO-639-1 language code to filter by, e.g. "en", "es", "ja".

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent nature. Description adds that it returns specific fields (streamer name, title, viewer count, thumbnail) and that game name is auto-resolved to ID, providing useful behavioral detail beyond annotations.

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?

Two sentences plus an example. Every part adds value with no redundancy. Highly efficient and front-loaded with the core action.

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?

Covers main purpose, filtering, and output fields. Lacks pagination details beyond the 'first' parameter, but given annotations and schema, it is sufficient for an agent to use correctly.

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 description's added value for individual parameters is limited. The example and note about omitting game provide some contextual meaning, but do not significantly enhance what the schema already conveys.

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?

Clearly states it gets live Twitch streams with optional game and language filters. Purpose is specific and actionable, but does not explicitly differentiate from sibling tools like top_games or search_channels.

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?

Provides context: omit game for overall top streams, and includes an example. However, it does not specify when to use this tool over alternatives or when not to use it.

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

All Twitch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

The tool set includes many similar Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded, ask_pipeworx_beta, deep_research) that all serve overlapping purposes, causing confusion. The Twitch-specific tools are distinct but are buried among many unrelated tools.

Naming Consistency3/5

Most tools use snake_case (e.g., get_streams, ask_pipeworx), but there is variation in patterns: some are verb_ noun (get_streams), some are just verbs (remember), and some are adjective_noun (recent_changes). No strong pattern across the whole set.

Tool Count2/5

With 35 tools, the server is bloated for its stated purpose as a 'Twitch' server. Only about 4-5 tools are Twitch-related; the rest are from a data platform (Pipeworx) and generic utilities, making the count feel excessive and unfocused.

Completeness2/5

For a Twitch server, the tool surface is severely incomplete. It lacks essential Twitch features like clips, follows, chat, or channel management. The few Twitch tools present cover only basic stream and user lookup.

Resources