Skip to main content
Glama
Sign In
StreamHub MCP

StreamHub MCP

by cristianodmtsb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

authenticate_platform

Authenticate YouTube, Twitch, or Kick from chat by triggering OAuth or setting platform credentials, so you can configure live-stream access before launching streams.

Instructions

Triggers authentication or sets credentials directly from chat for a platform (youtube, twitch, or kick).

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": {
      "platform": "<platform>"
    },
    "name": "authenticate_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoKick API key or token
clientIdNoOAuth Client ID for YouTube or Twitch
platformYesPlatform to authenticate: "youtube", "twitch", or "kick"
channelSlugNoKick channel slug / username (e.g. "meucanal")
clientSecretNoOAuth Client Secret for YouTube or Twitch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations, so the description carries the full burden, and it discloses almost nothing: whether it returns an auth URL, opens a browser, persists tokens, or overwrites existing credentials is unknown. For a tool that accepts secrets like clientSecret and apiKey, the absence of any note on storage or reversibility is a notable gap.

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?

A single front-loaded sentence with no filler. It is efficient, though partly because it omits detail rather than because it is tightly written.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five parameters, one required, secrets involved, no annotations and no output schema — this tool needs more than one sentence. Missing per-platform parameter requirements, what the call returns, and whether credentials are stored or validated.

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 baseline is 3; the schema already documents each parameter. The description misses the chance to add real value by explaining the per-platform parameter pairing (Kick needs apiKey/channelSlug, YouTube/Twitch need clientId/clientSecret), which the schema implies but never states.

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 action (authentication / credential setting) and the exact resource scope (youtube, twitch, kick), which distinguishes it from siblings like list_platforms or prepare_live. The dual mode ('triggers authentication OR sets credentials') is left ambiguous but the overall purpose is legible.

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?

No guidance on when to use this versus the OAuth flow, no prerequisites (e.g., must authenticate before prepare_live), and no indication of which mode applies in which situation. 'Directly from chat' hints at one path but is not an actionable condition.

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