Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av

wave_create_production

Create a new studio production with multi-camera support. Configure title, layout, stream sources, and recording settings.

Instructions

Create a new studio production with multi-camera support

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesProduction title
descriptionNoProduction description
layoutNoInitial layout mode (default: single)
stream_idsNoStream IDs to include as sources in the production
recordNoEnable recording for this production (default: false)

Implementation Reference

  • The handler function that executes the 'wave_create_production' tool logic. It builds a payload from the parameters (title, description, layout, stream_ids, record) and sends a POST request to /api/v1/studio/productions.
      async ({ title, description, layout, stream_ids, record }) => {
        const payload: Record<string, unknown> = { title };
        if (description !== undefined) payload["description"] = description;
        if (layout !== undefined) payload["layout"] = layout;
        if (stream_ids !== undefined) payload["stream_ids"] = stream_ids;
        if (record !== undefined) payload["record"] = record;
    
        const res = await waveFetch("/api/v1/studio/productions", {
          method: "POST",
          body: JSON.stringify(payload),
        });
        if (!res.ok) return errorContent(res.status, res.body);
    
        return textContent(res.body);
      },
    );
  • The input schema definition for the tool, defining parameters: title (required string 1-255 chars), description (optional string max 2000), layout (optional enum: single/split/pip/grid/custom), stream_ids (optional array of UUIDs), record (optional boolean).
    "Create a new studio production with multi-camera support",
    {
      title: z.string().min(1).max(255).describe("Production title"),
      description: z.string().max(2000).optional().describe("Production description"),
      layout: z
        .enum(["single", "split", "pip", "grid", "custom"])
        .optional()
        .describe("Initial layout mode (default: single)"),
      stream_ids: z
        .array(z.string().uuid())
        .optional()
        .describe("Stream IDs to include as sources in the production"),
      record: z
        .boolean()
        .optional()
        .describe("Enable recording for this production (default: false)"),
    },
  • The tool registration using server.tool() with name 'wave_create_production' inside the registerStudioTools function. This is how the tool is exposed to the MCP client.
    server.tool(
      "wave_create_production",
      "Create a new studio production with multi-camera support",
      {
        title: z.string().min(1).max(255).describe("Production title"),
        description: z.string().max(2000).optional().describe("Production description"),
        layout: z
          .enum(["single", "split", "pip", "grid", "custom"])
          .optional()
          .describe("Initial layout mode (default: single)"),
        stream_ids: z
          .array(z.string().uuid())
          .optional()
          .describe("Stream IDs to include as sources in the production"),
        record: z
          .boolean()
          .optional()
          .describe("Enable recording for this production (default: false)"),
      },
      async ({ title, description, layout, stream_ids, record }) => {
        const payload: Record<string, unknown> = { title };
        if (description !== undefined) payload["description"] = description;
        if (layout !== undefined) payload["layout"] = layout;
        if (stream_ids !== undefined) payload["stream_ids"] = stream_ids;
        if (record !== undefined) payload["record"] = record;
    
        const res = await waveFetch("/api/v1/studio/productions", {
          method: "POST",
          body: JSON.stringify(payload),
        });
        if (!res.ok) return errorContent(res.status, res.body);
    
        return textContent(res.body);
      },
    );
  • The waveFetch helper function used by the handler to make authenticated HTTP requests to the WAVE API.
    async function waveFetch(
      path: string,
      init?: RequestInit,
    ): Promise<{ ok: boolean; status: number; body: string }> {
      const url = `${getBaseUrl()}${path}`;
      const res = await fetch(url, {
        ...init,
        headers: {
          ...getAuthHeaders(),
          ...init?.headers,
        },
      });
      const body = await res.text();
      return { ok: res.ok, status: res.status, body };
    }
Behavior2/5

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

With no annotations, the description must disclose side effects, authorization needs, or limitations. It does not mention that creating a production may start recording (if 'record' is true) or that it requires a title. No behavioral traits beyond 'create' are shared.

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 description is a single, front-loaded sentence that efficiently communicates the core action. However, it could be slightly expanded to include essential usage context without sacrificing conciseness.

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?

No output schema exists, yet the description does not explain what the tool returns (e.g., production ID). It also lacks information about the multi-camera feature prerequisites or other configuration details, leaving the agent underinformed.

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?

Schema coverage is 100%, so the input schema already describes all parameters. The description adds no additional meaning beyond what is in the schema. For example, 'multi-camera support' hints at 'stream_ids' but is not explicit.

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?

The description 'Create a new studio production with multi-camera support' clearly states the verb (create), resource (studio production), and a distinguishing capability (multi-camera support). It effectively differentiates from siblings like 'wave_create_clip' and 'wave_create_stream'.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention that 'wave_list_productions' is for listing or that 'wave_create_clip' is for creating clips. The agent must infer usage context from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wave-av/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server