Skip to main content
Glama

get_live_stream_key

Read-onlyIdempotent

Return stream_key so the user can paste it into OBS or ffmpeg.

This is the only live tool that returns the key. On success the body is
only `stream.id`, `stream.stream_key`, and `stream.ingest` (RTMP, RTMPS,
and `host` after start). Status, playback, and DVR are not in this
response — read them with `get_live_stream`. Give the key to the user
with the ingest URL. Do not put it in another tool argument.

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

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

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the exact scope of the response, which fields are deliberately absent, that `host` only appears after start, and a security-relevant handling rule against passing the secret to another tool. That is substantive behavioral context the annotations cannot convey.

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-loaded with the capability and the key value proposition, then scoping and handling rules in tight sentences. Slight redundancy in enumerating `stream.id`, `stream.stream_key`, and `stream.ingest` when an output schema already exists, but nothing else is wasted.

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 read tool with an output schema, the description covers purpose, sibling routing, response boundaries, and secret-handling. An agent has everything needed to select and invoke it correctly.

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?

Only one parameter, documented at 100% schema coverage with a pattern and length bounds, so the schema already carries the semantics. The description implies the id is a live stream id but adds no additional meaning about it; baseline 3 applies.

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?

Names a specific verb and resource ('Return `stream_key`') plus the concrete user goal (paste into OBS or ffmpeg), and explicitly separates itself from siblings by stating it is the only live tool that returns the key. An agent can distinguish it from get_live_stream without opening any schema.

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 both sides of the routing decision: use this tool when the key itself is needed, and read status, playback, and DVR via `get_live_stream` instead. It also adds operational guidance ('Give the key to the user with the ingest URL. Do not put it in another tool argument.'), leaving nothing 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.