Skip to main content
Glama
Podcast MCP
by calebn

create_record_room_tool

Mint a recording room with guest and producer /rec/ links, revoke earlier room links, and optionally save an unsaved take before minting.

Instructions

Mint a recording room: guest + producer /rec/ links; revokes earlier rooms' links (docs/recording-session.md).

If the current room has a stopped take not saved to the episode, the result says so (unlanded_take, unlanded_takes, unlanded_saving, unlanded_stalled, land_first_possible, warning) and the mint still happens. Pass land_first to save that take first (result adds landed_first; audio that never finished uploading cannot be saved; every mint that leaves audio the server detected as never finished reports left_behind (a count) and left_behind_message). Land-first mints nothing and keeps the old links when uploads are still saving (wait until 10 minutes pass with no upload and no rejoin from that person since Stop, or mint without it), when the room's staged session was already accepted or skipped and something is landable or saving, or when the land leaves a take unsaved.

target is where the session lands: end (the default), start (the front of the episode), or an insert/replace JSON object that stages the session as a suggestion.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_record_room_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo
expires_atNo
land_firstNo
project_pathNo
public_base_urlNohttp://127.0.0.1:8765

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.4
    • addedInput schema / properties / land_first
      Added value: +{
      +  "default": false,
      +  "title": "Land First",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / target
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Target"
      +}
  2. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does substantial work: it discloses the destructive side effect (revoking earlier rooms' links), the non-fatal warning behavior when a take is unlanded, the specific blocking conditions for land_first, and the left_behind reporting for never-uploaded audio. It omits permissions/auth requirements and idempotency, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the second sentence is a dense run-on packing three separate blocking conditions and nested parentheticals into one clause chain that is hard to parse on first read. Every clause carries information, so it is not padding, but the structure could be broken into conditions the agent can scan.

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

Completeness3/5

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

An output schema exists, yet a large share of the text enumerates return fields (unlanded_take, left_behind, landed_first) rather than filling genuine gaps. The real gaps — the three undocumented input parameters and any auth/prerequisite context for a link-revoking mint — remain unfilled, so the description is rich but misallocated relative to the tool's complexity.

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 description coverage is 0%, so the description must compensate: it explains target's four accepted forms (end, start, insert/replace JSON object) and exhaustively covers land_first's semantics and failure modes. However, expires_at, project_path, and public_base_url — three of five parameters — get no mention anywhere, so compensation is partial.

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 first clause names a specific verb and resource ('Mint a recording room') and immediately specifies the artifacts produced (guest + producer /rec/ links) plus the side effect of revoking earlier rooms' links. It is clearly distinguishable in substance, but it never names a sibling (e.g., revoke_record_room_tool, record_start_tool) to route against, so it stops short of a 5.

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?

Tool-level guidance is only implied: the agent must infer that you call this to open a session before recording. The detailed when/when-not text all concerns the land_first parameter rather than whether to use this tool versus alternatives, so the usage guidance is present but scoped to a flag rather than the tool choice.

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