Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Remove recording

remove_recording
DestructiveIdempotent

Delete a recording and cancel any in-progress edits, while posts already made from its clips remain in Scheduling. The first call only previews the removal and returns a confirmation for a second call.

Instructions

Removes a recording and stops any editing in progress. Posts already created from its clips stay in Scheduling. The first call removes nothing and returns needs_confirmation, will_happen and confirmation; removal happens only on a second call with that confirmation.

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": {
      "recording_id": "<recording_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "remove_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
confirmationNo
recording_idYesThe recording's id, from list_recordings.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the destructiveHint/openWorldHint annotations, it discloses what is destroyed and what is preserved ("Posts already created from its clips stay in Scheduling") and details the two-phase confirmation contract with the exact response fields. This is precisely the behavior an agent could not infer from the annotations alone.

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?

Three tight sentences, front-loaded with the verb and side effect, then the data-preservation caveat, then the confirmation mechanic. No filler or redundancy.

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 destructive four-parameter tool with no output schema, the description covers the risk profile, the confirmation handshake, and the first-call return fields. The only real gap is the purpose of idempotency_key and the shape of a successful removal response.

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 only 25%, and the description compensates for confirmation by restating its two-call semantics, though that largely duplicates the schema text. It says nothing about idempotency_key or account_id, which remain undocumented in both places.

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 opening sentence names a specific verb and resource ("Removes a recording") and adds a meaningful side effect ("stops any editing in progress"). It doesn't explicitly contrast with siblings like recut_recording or get_recording, but the destructive intent is unambiguous.

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

Usage Guidelines4/5

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

The description gives clear operational guidance: the first call is a dry run, removal only occurs on a second call carrying the returned confirmation. It doesn't state when a user should prefer this over alternatives such as recut_recording, so it stops short of full alternative routing.

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