Skip to main content
Glama

Twitch

by io.github.pipeworx-io

Search Channels

search_channels
Read-onlyIdempotent

Search Twitch channels/streamers by name or keyword. Returns matching channels with display name, the game they stream, whether they are live now, title, and thumbnail. Example: search_channels({ query: "ninja", live_only: true })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNoNumber of channels to return (default 20, max 100)
queryYesSearch query — channel/streamer name or keyword, e.g. "ninja", "valorant".
_apiKeyNoOptional — your own Twitch credentials as CLIENT_ID:CLIENT_SECRET for higher limits; omit to use the shared Pipeworx key.
live_onlyNoIf true, only return channels that are currently live.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds return fields and an example, but does not discuss pagination, rate limits, or behavior with empty queries.

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 and an example: no wasted words. Front-loaded with verb and resource, then example. Excellent conciseness.

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 no output schema, the description explains return fields well. It could mention pagination (first param) and error handling for no results, but overall it is sufficiently complete for a simple search tool.

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 each parameter is documented. The description adds an example demonstrating query and live_only usage, but does not provide additional semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches Twitch channels/streamers by name or keyword, and lists returned fields (display name, game, live status, title, thumbnail). This distinguishes it from sibling tools like get_user (single user) or get_streams (streams not 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?

The description implies usage for finding channels but does not explicitly state when to use this tool vs alternatives like get_user or get_streams. No guidance on when not to use or prerequisites.

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