Skip to main content
Glama
Sign In

Twitch

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-twitch-api-key",
-    "query": "ninja"
-  },
-  {
-    "_apiKey": "your-twitch-api-key",
-    "first": 25,
-    "live_only": true,
-    "query": "valorant"
-  }
-]New value: +[
+  {
+    "query": "ninja"
+  },
+  {
+    "first": 25,
+    "live_only": true,
+    "query": "valorant"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-twitch-api-key",
+    "query": "ninja"
+  },
+  {
+    "_apiKey": "your-twitch-api-key",
+    "first": 25,
+    "live_only": true,
+    "query": "valorant"
+  }
+]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds the return payload shape (display name, game, live status, title, thumbnail), which is meaningful behavioral context since no output schema exists.

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?

Two tight sentences plus an example; the core purpose is front-loaded and nothing rambles. The inline example is mildly redundant given the schema already carries examples, keeping it just shy of a 5.

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 read-only search tool with full schema coverage and no output schema, the description supplies the missing return-value context (the fields returned). It omits pagination/total-count behavior, but the essential picture is 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%, with each parameter (first, query, _apiKey, live_only) already documented in the schema. The description's example repeats query/live_only usage without adding format or edge-case semantics, so this sits at the schema-driven baseline.

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 ('Search Twitch channels/streamers by name or keyword'), so the agent knows exactly what it does. It does not, however, distinguish itself from plausible siblings like get_user, get_streams, or top_games, which an agent could easily confuse with channel search.

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?

Usage is only implied through the inline example (searching 'ninja' with live_only). There is no explicit statement of when to use this over get_user/get_streams or any prerequisite/limit guidance, leaving routing to inference.

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
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