Skip to main content
Glama
Sign In
StreamHub MCP

StreamHub MCP

by cristianodmtsb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

prepare_live

Prepare and update live broadcast settings for selected platforms such as YouTube, Twitch, and Kick, including titles, descriptions, tags, game categories, thumbnails, and privacy.

Instructions

Prepares and updates live broadcast configuration across selected platforms (YouTube, Twitch, 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": {
      "platforms": "<platforms>",
      "title": "<title>",
      "description": "<description>"
    },
    "name": "prepare_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoGame name for automated category and tag detection
titleYesStream title
partnersNoSponsors, partners or co-streamers mentions
isPrivateNoWhether the stream should be private/unlisted (for tests)
platformsYesTarget platforms (e.g. ["all"] or ["youtube", "twitch", "kick"])
customTagsNoAdditional custom tags
descriptionYesMain topic/summary of the stream
templateNameNoTemplate to use (default: "default")
thumbnailPathNoLocal path to the thumbnail image file

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 are supplied, so the description carries the full behavioral burden and does almost none of it. It implies a mutation ("prepares and updates") but never states that it writes to real platforms, whether existing broadcast settings are overwritten, what authentication or scopes are required, whether it is idempotent, or whether it can partially succeed when only some platforms are selected.

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 the resource stated before the platform parenthetical; nothing is padded or redundant. It is arguably too terse for a 9-parameter mutation, but no sentence wastes space.

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

Completeness3/5

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

For a high-complexity, 9-parameter write tool with no annotations and no output schema, an agent still lacks prerequisites, overwrite semantics, and per-platform failure behavior. The description is complete enough to identify the operation but not complete enough to call it safely in a multi-platform broadcast workflow.

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 9 well-described parameters, so the schema already documents game, thumbnailPath, templateName, isPrivate and the rest. The description only reinforces the platforms list and adds no format details, defaults, or interaction rules (e.g. how customTags combine with auto-detected tags) beyond schema text, making the baseline 3 appropriate.

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 concrete verb pair ("prepares and updates") and a specific resource ("live broadcast configuration") narrowed to named platforms YouTube, Twitch and Kick. An agent understands the action, but the description never differentiates this from the sibling preview_live_metadata or explains where preview ends and this begins.

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?

There is no explicit when-to-use or when-not-to-use guidance. Given siblings like preview_live_metadata and authenticate_platform, the description should say whether authentication must precede it or whether a preview should be run first; it mentions none of this, leaving sequencing entirely to inference.

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