Skip to main content
Glama
Sign In
StreamHub MCP

StreamHub MCP

by cristianodmtsb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

preview_live_metadata

Preview rendered live stream metadata—description, tags, and categories—before publishing, so you can verify and adjust settings without going live.

Instructions

Generates a preview of live metadata (rendered description, tags, categories) without publishing.

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": {
      "title": "<title>",
      "description": "<description>"
    },
    "name": "preview_live_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoGame name for automated category and tag detection
titleYesStream title
partnersNoSponsors, partners or co-streamers mentions
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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully discloses that the tool does not publish, which is a key non-mutation trait, and names the rendered preview contents, but it omits authentication prerequisites, side effects around thumbnail or template handling, and return-shape details.

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?

The definition is a single tightly written sentence with no filler. The core action and the non-publishing constraint are front-loaded, and every phrase contributes information.

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 seven-parameter tool with no annotations and no output schema, the description gives the essential purpose, non-publishing behavior, and a partial view of returned metadata. It still leaves out platform authentication expectations, template and thumbnail behavior, and a fuller account of the preview response.

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 all seven parameters are already documented in the input schema. The description adds no parameter-specific meaning beyond the schema, such as how game detection interacts with title and description or how templateName affects the preview, so the baseline of 3 applies.

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?

The description uses a specific verb ('Generates a preview') and resource ('live metadata'), and enumerates preview contents (rendered description, tags, categories). It clearly distinguishes the action from publishing, but does not explicitly differentiate from the sibling prepare_live.

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 phrase 'without publishing' implies this is a preview-only step, likely useful before prepare_live or publishing. However, there is no explicit when-to-use guidance, no named alternative, and no exclusions for cases where a different sibling should be called.

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