Skip to main content
Glama

start_recording

Start a call or conversation recording from system audio or apps like WhatsApp, Teams, Zoom, and browsers, with optional microphone capture and local transcription.

Instructions

Start recording a call or a conversation.

source: "system" (all the Mac's audio, the safest), "whatsapp", "teams", "zoom", "slack", "facetime", "browser" (all browsers), "chrome", "safari", "firefox", "arc", "edge", or a bundle ID prefix (e.g. "com.microsoft.teams2"). title: name of the conversation (used for the folder name). include_mic: also record the microphone (the user's voice). language: transcription language ("en", "fr", "auto"...). Defaults to the user's language. speakers: number of people on the other side (default 1). Above 1, their voices are separated in the transcript (Speaker 1, Speaker 2...). live: also transcribe as the call goes, to follow it with get_live_transcript. Use it when the user wants help during the call (questions to ask, answers to dig into).

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": "start_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNo
titleNo
sourceNosystem
languageNo
speakersNo
include_micNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / live
      Added value: +{
      +  "default": false,
      +  "title": "Live",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: which audio source is captured, whether the microphone is included, speaker separation above one speaker, and that live mode enables get_live_transcript. It does not explain permissions, where recordings are stored, or what happens if a recording is already active.

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 purpose is front-loaded and the parameter explanations are compact. The long enumerations of sources and transcription languages are useful but make the description longer than strictly necessary.

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 six-parameter start-recording tool with no required parameters, the description covers every parameter and the live-recording workflow. An output schema exists, so return values need not be explained, but lifecycle details such as how to stop or what happens on repeated starts are omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 carry the full burden, and it does: it defines source with concrete values and a bundle-ID option, explains title, include_mic, language and speakers along with defaults, and explains live. This adds substantial meaning beyond the bare schema property names.

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 opens with a specific verb and resource: "Start recording a call or a conversation." It also enumerates sources and explains live transcription, so an agent can distinguish it from stop_recording and the transcript-focused siblings without inspecting the schema.

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?

It gives clear situational guidance for source selection ("system" is safest) and for live mode ("Use it when the user wants help during the call"), and it references get_live_transcript. It does not explicitly state when not to use this tool or that stop_recording must eventually be called.

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