Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Add recording

add_recording
Idempotent

Import a public video or audio file from a direct URL as a new recording and start generating clips from it; use the returned recording ID and status to track processing.

Instructions

Brings in an existing video or audio file from a direct link as a new recording and starts editing it into clips, which takes several minutes. Counts against the account's recording allowance. Returns the new recording's id and status.

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": {
      "media_url": "<media_url>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "add_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
media_urlYesPublic https link that points directly at a video or audio file, up to 1 GB.
account_idNo
instructionNoOptional guidance for the edit, such as which topics to cut clips from.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the job 'takes several minutes' (long-running/asynchronous), 'Counts against the account's recording allowance' (quota cost), and the return shape ('id and status'), signaling a poll-or-wait pattern with wait_for_recording/get_recording. It stops short of saying what to do while waiting or whether the source link is fetched immediately.

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 action, then cost/duration, then return value. No filler or restatement of the title, and each sentence carries information the agent needs before calling.

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 5-parameter, non-destructive mutation with no output schema, the definition covers duration, quota consumption and the return payload, which is what an agent most needs. Gaps remain around the required idempotency_key's retry semantics and the untouched title parameter, but nothing essential to invoking it correctly is missing.

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 only 40%: media_url and account_id are documented in the schema, while title, instruction and idempotency_key are bare. The description reinforces media_url ('direct link') and loosely touches the edit instruction ('starts editing it into clips'), but says nothing about idempotency_key being required or what a retry with the same key does, and nothing about title or account_id.

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?

States a specific verb and resource ('Brings in an existing video or audio file from a direct link as a new recording') plus the downstream effect ('starts editing it into clips'). The 'direct link' qualifier implicitly separates it from the upload siblings (create_recording_upload / finish_recording_upload), so an agent can pick it without opening a schema.

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?

The phrase 'existing video or audio file from a direct link' gives an implied precondition for use, which is more than nothing. However, it never names alternatives such as create_recording_upload (file upload) or start_browser_recording, nor does it state when this tool is the wrong choice. Usage must be inferred from the source-type hint.

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