Skip to main content
Glama

start_live_stream

Allocate the encoder for a live stream.

Required before WebRTC or SRT ingest. Call it before an RTMP publish
too: auto-start works only if a free transcoder is available within
about 15 seconds. Otherwise the stream goes to `stopped` and the
publish is rejected. If the user explicitly asked to start with a
protocol other than this stream's current `input_format`, call
`update_live_stream` on this same id first. Call this tool only if the
stream is not already running. Do not start a different stream instead.
The response
`ingest.host` is the encoder host; SRT and WebRTC URLs are not included.
Already started comes back as `code: live_api_error` (live API 406). Do
not retry that. A 504 is `code: live_timeout`, also a normal result.
Do not retry it either. Call `get_live_stream`: the stream may already
be `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>"
    },
    "name": "start_live_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior5/5

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

Annotations only tell the agent this is a non-read-only, non-idempotent, non-destructive, closed-world call; the description goes well beyond that. It discloses the auto-start timeout window, the resulting `stopped` state and rejected publish, the response field `ingest.host` and the fact that SRT/WebRTC URLs are not returned, and it maps both the 406 `live_api_error` (already started) and the 504 `live_timeout` to normal, non-retryable outcomes. That is exactly the behavioral context annotations cannot carry.

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?

The core action and the primary precondition are front-loaded, and nearly every sentence carries distinct operational value (protocol prerequisites, timeout, error codes, do-not-retry, recovery call). It is slightly fragmented by hard line breaks and the closing "Call `get_live_stream`: the stream may already be `stopped`" reads as a truncated lead-in, plus the repeated "Do not retry" phrasing could be consolidated.

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

Completeness5/5

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

For a one-parameter mutation with an output schema, the description supplies everything needed to call it correctly and to interpret both success and failure: prerequisites, ordering with update_live_stream, the state transition on timeout, and the meaning of both documented error codes. Nothing an agent needs in order to invoke this safely is missing.

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?

There is only one parameter and schema description coverage is 100%, with a pattern and length bounds already documenting `stream_id`, so the schema carries the burden. The description adds a little indirect meaning by referencing "this stream's current `input_format`" and "this same id," implying the id identifies a pre-existing configured stream. Beyond that it adds no syntax or format detail, which matches the baseline for a fully documented single parameter.

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?

"Allocate the encoder for a live stream" is a specific verb-plus-resource statement that tells the agent what starting actually means (an encoder allocation, not just a state flip). It is further narrowed by "Call this tool only if the stream is not already running" and "Do not start a different stream instead," which constrain scope. It stops short of explicitly distinguishing itself from the sibling start_encode2_raw, so it is clear but not fully sibling-differentiated.

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?

The description gives explicit when-to-use conditions (required before WebRTC or SRT ingest, recommended before RTMP publish), the precondition for the optimistic path (a free transcoder within ~15 seconds), and the routing rule when a different protocol is wanted (call update_live_stream on the same id first). It also states the correct follow-up on failure (call get_live_stream, since the stream may be stopped) and forbids the wrong action (do not start a different stream, do not retry 406/504).

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.