Skip to main content
Glama

update_live_stream

Destructive

Change a live stream. Pass at least one change.

To switch ingest protocol, set `input_format` (`rtmp`, `webrtc`, or
`srt`) on the stream id the user named. Changing protocol does not
require starting or stopping the stream. Do not change its status
unless the user also asked to start or stop it. QA accepts this update
in `created`, `waiting`, `live`, `idle`, and `stopped`, and the status
stays the same. Do not create or start a different stream that already
uses the requested protocol.
WebRTC and SRT ingest URLs are not in this response. Tell the user to
open this stream in the portal for those URLs.

DVR records only to Qencode Media Storage. `dvr_bucket` must be a bucket
from `list_buckets`. Do not send storage keys or secrets; the portal
builds the destination. Enabling DVR needs a destination now or from an
earlier update. An empty `callback_url` clears the callback.

`code: nothing_to_update` means no field was sent. `bucket_not_found` and
`storage_not_ready` mean the bucket is missing or Media Storage is not
enabled — do not invent a bucket.

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": "update_live_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew stream name.
dvr_pathNoFolder inside dvr_bucket. Requires dvr_bucket.
stream_idYesLive stream id.
dvr_bucketNoOwner's Media Storage bucket, from list_buckets.
dvr_enabledNoRecord to Qencode Media Storage. Needs dvr_bucket.
callback_urlNoHTTPS callback. Pass an empty string to clear it.
input_formatNoSwitch this stream to rtmp, webrtc, or srt.
output_formatNoPlayback packaging.

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.6/5.0
Behavior4/5

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

Annotations flag a destructive, non-idempotent, open-world write; the description adds real substance on top — which QA states accept the update, that status is preserved, and that empty callback_url clears the callback. It doesn't explicitly discuss reversibility of a change or that DVR destination cannot be unset, which would fully round out a destructive tool, so it stops short of 5.

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?

Front-loads the verb, resource, and the 'at least one change' rule, then groups protocol, DVR/callback, and error semantics into short paragraphs that each carry information. It is long for a field-update tool and the 'do not create or start a different stream' line slightly overlaps the sibling guidance, but nothing is filler.

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?

An output schema exists, so return shape needn't be described; the description instead covers the things schema cannot — accepted state transitions, protocol-switch side effects, DVR prerequisites, and error-code meanings, including the note that WebRTC/SRT ingest URLs are absent from the response. That is complete for an 8-parameter destructive update.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 3 is the baseline; the description exceeds it by documenting cross-parameter relationships the schema states only loosely — dvr_enabled needing a destination now or from a prior update, dvr_bucket needing list_buckets, and empty string clearing callback_url. It adds meaning rather than restating field titles, though output_format is left unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Change a live stream') and immediately bounds scope with 'Pass at least one change.' It also fences off what siblings do — status changes (start/stop) and creating another stream — so an agent can separate this from start_live_stream, stop_live_stream, and create_live_stream without opening their schemas.

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?

Gives explicit when-to and when-not-to guidance: don't change status unless the user asked to start or stop, don't create/start a different stream on the requested protocol, and protocol switches need no restart. It also states preconditions for DVR (bucket from list_buckets, destination now or from an earlier update) and interprets error codes, leaving little to inference.

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.