Skip to main content
Glama

Upstream.so

by so.upstream.studio
OverviewDiscussionsAdmin

Update Stream

update_stream
DestructiveIdempotent

Partially update a stream (PATCH semantics: only provided fields change). Same fields as create_stream except type (creation-only). May overwrite settings or tags and affect live output or scheduled starts/stops. Mirrors PATCH /api/v1/streams/{stream}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoStream key. custom, instagram or rumble: must start rtmp:// or rtmps://; customsrt: srt://.
urlNoIngest URL override, or null to clear it.
nameNoStream name, max 100 chars.
tagsNoTag names to attach (replaces the existing set; missing names are created).
streamYesStream UUID.
volumesNoVolumes 0-100: main, secondary, video.
encodingNoEncoding settings: resolution, frame_rate, bitrate, audio_bitrate (128-328).
platformNoTarget platform, e.g. youtube, twitch, kick, custom, customsrt.
playbackNoPlayback: mode (loop|single), video_order (loop|shuffle), audio_order (loop|shuffle), default_image_duration (1-3600s).
scheduleNoSchedule: is_scheduled/scheduled_at (start), is_scheduled_end/scheduled_end_at (end), repeat_schedule (boolean), mode (null|continuous), continuous_start_type (now|scheduled), continuous_stop_type (never|scheduled), continuous_stop_at, stream_duration_hours/stream_duration_minutes and break_duration_hours/break_duration_minutes (continuous mode active/break time per cycle, each combo >=5min), preserve_state (resume playback after a continuous-mode cycle restart; cannot change while the stream is live).
recordingNoRecording: enabled (boolean).
video_fitNoVideo fit: object_fit (cover|contain), style, background_color.
descriptionNoDescription, or null to clear it.
transitionsNoTransitions: fade_duration (0-20), animation_type (random|fade|slide|scale|swipeAway), animation_duration (0-20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint and idempotentHint, so the bar is lower. The description still adds real value: PATCH semantics (only supplied fields change) and explicit warnings that it may overwrite settings/tags and affect live output or scheduled start/stop behavior.

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?

Single compact paragraph, front-loaded with the core verb and PATCH semantics, then warnings. Every clause carries weight; not padded, though the create_stream cross-reference requires the reader to know that sibling.

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 14-param destructive mutation with nested objects and no output schema, the description covers semantics, side-effect scope, and endpoint parity. It omits auth/permission requirements and return behavior, but annotations plus rich schema cover most of the remaining need.

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?

With 100% schema description coverage the schema already documents all 14 parameters, so baseline 3 applies. The description adds only a cross-reference ('same fields as create_stream except type'), which gives some semantics but no per-parameter detail.

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?

States a specific verb (partially update), resource (a stream), and defines the update style via PATCH semantics. It distinguishes itself from create_stream by noting type is creation-only, but does not differentiate from other update_* siblings.

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?

Implies use for modifying an existing stream and cross-references create_stream for the field set, giving useful context. However it never states when to prefer this over alternatives or any prerequisites (e.g., permissions, live-state conditions).

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

All Upstream.so toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources