Skip to main content
Glama

Add a take

add_take

Add a recording to a project as a take of a scene: screen, camera and/or audio files (uploads/... or public https). Ingest runs in the background (remux, clean audio, transcribe with filler words): poll get_task with the task_id. Costs 4 credits per started recorded minute, charged once ingest knows the length; get_task reports them. The newest take of a scene is used once it's ready.

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": {
      "project_id": "<project_id>"
    },
    "name": "add_take"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioNoSeparate mic track; otherwise the first video's own sound is used
cameraNo
screenNoScreen recording: uploads/... or a public https URL
offsetsNo
scene_idNoOmit to start a new scene
project_idYesFrom create_project
scene_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false. The description adds valuable context beyond them: background ingest steps (remux, clean audio, transcription with filler words), cost of 4 credits per started recorded minute charged after ingest knows the length, and newest-take-wins semantics. It does not contradict the annotations; failure or cancellation behavior is the main omission.

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?

Front-loads the purpose, then follows with background behavior and cost in compact sentences. It is somewhat dense but every sentence carries useful information, with no filler.

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?

With no output schema, the description covers the asynchronous workflow, credit cost, and scene-take selection semantics well. It leaves gaps around the offsets and scene_title parameters and lacks explicit failure behavior, but is adequate for a 7-parameter mutation tool.

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 57%, so the schema documents several parameters including audio fallback, screen URL format, scene_id omission, and project_id source. The description adds meaning for camera/screen/audio as take sources but does not clarify offsets or scene_title, which remain undocumented in both places.

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: adding a recording as a take of a scene, enumerating screen, camera, and/or audio files with accepted URI forms. It clearly distinguishes this from siblings such as add_scene or add_screens by naming the take-of-a-scene concept.

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?

Explains the workflow: ingest runs in the background, so poll get_task with the task_id, and the newest take of a scene is used once ready. It gives clear context but does not explicitly exclude or compare against alternatives like add_screens or add_graphic.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources