Skip to main content
Glama
Sign In

Twitch

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-twitch-api-key",
-    "first": 20
-  },
-  {
-    "_apiKey": "your-twitch-api-key",
-    "first": 20,
-    "game": "Fortnite",
-    "language": "en"
-  }
-]New value: +[
+  {
+    "first": 20
+  },
+  {
+    "first": 20,
+    "game": "Fortnite",
+    "language": "en"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-twitch-api-key",
+    "first": 20
+  },
+  {
+    "_apiKey": "your-twitch-api-key",
+    "first": 20,
+    "game": "Fortnite",
+    "language": "en"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuine behavioral detail beyond that — the exact fields returned (streamer name, title, viewer count, thumbnail) and the default behavior when `game` is omitted.

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?

Three sentences, front-loaded with the purpose, then the return fields, then the key behavioral rule and an example. Every sentence earns its place with no redundancy.

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?

No output schema exists, so the description correctly fills that gap by enumerating returned fields, and annotations cover the safety profile. A read tool with 0 required params is well-specified, with only minor gaps (e.g., no note on pagination or the shared-key rate limit already surfaced in the schema).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that omitting `game` yields the overall top streams and by showing a concrete invocation with `first` and `language` combined. That is more than the schema's per-field prose.

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 ('Get live Twitch streams') and scopes it with the optional filters. It is unambiguous what the tool returns, though it does not explicitly distinguish itself from sibling Twitch 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context: use filters for specific games/languages, and 'Omit `game` for the overall top live streams across Twitch.' This tells the agent when the parameters matter, but offers no explicit when-not-to-use or named alternative tool.

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