Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wave_create_stream

Set up a new live stream by creating a Cloudflare Stream input with configurable title, privacy, protocol, recording, and metadata.

Instructions

Create a new stream (POST /v1/streams) with a Cloudflare Stream live input

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesStream title
privacyNoStream visibility (default: public)
metadataNoArbitrary metadata to attach
protocolNoIngest protocol (default: auto)
recordingNoRecording configuration for this stream
descriptionNoStream description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / description / maxLength
      Previous value: -2000New value: +5000
    • addedInput schema / properties / metadata
      Added value: +{
+  "additionalProperties": {},
+  "description": "Arbitrary metadata to attach",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedInput schema / properties / privacy
      Added value: +{
+  "description": "Stream visibility (default: public)",
+  "enum": [
+    "public",
+    "private"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / protocol / description
      Previous value: -"Streaming protocol (default: webrtc)"New value: +"Ingest protocol (default: auto)"
    • changedInput schema / properties / protocol / enum
      Previous value: -[
-  "webrtc",
-  "srt",
-  "rtmp",
-  "hls"
-]New value: +[
+  "webrtc",
+  "srt",
+  "rtmp",
+  "auto"
+]
    • removedInput schema / properties / record
      Removed value: -{
-  "description": "Enable recording for this stream (default: false)",
-  "type": "boolean"
-}
    • addedInput schema / properties / recording
      Added value: +{
+  "description": "Recording configuration for this stream",
+  "properties": {
+    "enabled": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "enabled"
+  ],
+  "type": "object"
+}
    • removedInput schema / properties / region
      Removed value: -{
-  "description": "Preferred ingest region (e.g., us-east-1, eu-west-1)",
-  "type": "string"
-}
    • changedInput schema / properties / title / maxLength
      Previous value: -255New value: +200
  2. First observedv0.1.5

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only conveys that this is a creation mutation. It does not state permissions, quota/cost implications, whether the stream starts immediately, or what the response contains (e.g., stream ID, ingest URL). The Cloudflare Stream live input detail adds some context but not enough to cover side effects or return behavior.

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 description is a single sentence with no filler; the key verb, resource, and endpoint appear early. The Cloudflare Stream live input detail is the only extra context and it earns its place. This is appropriately front-loaded and concise.

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

Completeness2/5

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

For a create operation with no annotations and no output schema, the description is too thin: it omits what the created stream looks like, what is returned, and how creation relates to starting the stream. The schema covers parameter formats well, but the tool-level behavior and downstream workflow are missing. A minimally complete description would at least mention that creation is separate from starting and returns a stream identifier or ingest credentials.

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?

The input schema already covers all six parameters with descriptions, enums, and defaults, so schema description coverage is 100%. The description itself adds no parameter-level meaning, but per the high-coverage baseline, a score of 3 is appropriate. No parameter semantics are sufficiently missing to lower the score.

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?

The description clearly states a create action on a stream resource and includes the REST endpoint, so the agent knows exactly what operation this is. It is not tautological and the verb 'create' distinguishes it from list/start/stop siblings, but it does not explicitly contrast itself with those siblings.

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

Usage Guidelines2/5

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

The description gives no conditions for when to create a stream versus listing, starting, or stopping one, and it names no alternatives. The verb implies creation is the intended use, but there are no prerequisites, exclusions, or routing cues. The agent is left to infer context from the tool name and siblings.

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

Deploy Server

Other Tools