Skip to main content
Glama

add_playback_id

Add a playback id. Prefer policy: public unless the user asked otherwise.

An `authenticated` id is created, but nothing here can sign viewer
tokens, so viewers cannot play it from this connector. Refused with
`code: stream_active` while the stream is starting, waiting, launching,
live, or idle, because the live API would stop the broadcast. Do not
retry until the stream is stopped.

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": {
      "stream_id": "<stream_id>",
      "policy": "<policy>"
    },
    "name": "add_playback_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYespublic is watchable via playback_url. authenticated cannot be signed here.
stream_idYesLive stream id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / stream_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
  2. Added
  3. Removed
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses a real functional limitation — an authenticated id is created but no viewer tokens can be signed here, so viewers cannot play it — and describes the failure mode with a specific error code (stream_active) and its cause. It does not need to restate the mutation/safety profile the annotations already carry.

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 action and default come first, followed by the authenticated caveat and the refusal/retry rule. Each sentence carries a distinct operational fact with no filler.

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 two-parameter mutation with an output schema, the description supplies what the schema cannot: the policy default, the token-signing limitation, and the refusal code with retry guidance. Only the return-value shape is left implicit, which is appropriate given the output schema.

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% and the enum for policy already documents that public is watchable via playback_url while authenticated cannot be signed here. The description only echoes that tradeoff in the “Prefer policy: public” line, adding no new syntax or format detail beyond the schema.

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?

"Add a playback id" states a specific verb and resource, and the description names the object that matters (viewer playback via a playback id). It does not explicitly differentiate from the sibling remove_playback_id, but the operation is unambiguous on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit default ("Prefer policy: public unless the user asked otherwise") plus concrete when-not conditions: refused while the stream is starting, waiting, launching, live, or idle, and an explicit retry instruction ("Do not retry until the stream is stopped"). An agent knows both which policy to pick and when the call will fail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.