Skip to main content
Glama

start_recording

Capture screen recordings on macOS, iOS Simulator, or Android. Specify target and optional duration, then use returned session_id to stop recording later.

Instructions

Start recording a macOS, iOS Simulator, or Android screen target.

Target aliases:
- macOS: "macos", "mac", or "desktop"
- iOS Simulator: "ios_simulator", "ios-simulator", "ios", or "simulator"
- Android: "android"

Common options include orientation and rotate_degrees. macOS options include
region, display, include_cursor, include_clicks, and include_audio. iOS
Simulator options include device, udid, and display ("internal" or
"external"). Android options include serial, size, and bit_rate.

Omit duration_seconds for the preferred manual-stop workflow, then call
stop_recording with the returned session_id. The response includes
session_id, video_path, target, mode, started_at, pid, and target_key.

macOS recording requires Screen Recording permission for the launcher
process. For browser or desktop-app debugging, prefer
start_app_window_recording so the visible app window is checked and only
that window region is recorded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesBackend alias: 'macos'/'mac'/'desktop' for screencapture, 'ios_simulator'/'ios'/'simulator' for xcrun simctl, 'android' for adb.
duration_secondsNoSeconds to record. Omit for manual-stop workflow (call stop_recording later).
output_pathNoAbsolute path for the output file. Defaults to $VIDEO_CAPTURE_MCP_OUTPUT_DIR or system temp under video-capture-mcp.
optionsNoBackend-specific dict. macOS: region/display/include_cursor/include_clicks/include_audio. iOS Simulator: device/udid/display. Android: serial/size/bit_rate. Cross-backend: orientation, rotate_degrees.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses important behavioral traits: macOS requires Screen Recording permission, describes workflow with stop_recording, and lists response fields. Without annotations, description carries burden and does so well, though could mention potential limitations like concurrent sessions.

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?

Well-structured with clear sections: general purpose, target aliases, options breakdown, workflow guidance, response info, permission note, and sibling pointer. Every sentence adds value with no 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?

Covers multiple platforms, options, workflow choices, permission requirements, and alternative tools. Lacks details on error handling or concurrent recording limitations, but overall complete for a tool of this complexity.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: target alias mapping, platform-specific options details, workflow guidance for duration_seconds, and response content preview. Enhances understanding beyond schema.

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?

Description clearly states it starts recording a macOS, iOS Simulator, or Android screen target. It distinguishes from sibling tools like start_app_window_recording and stop_recording, which are explicitly mentioned as alternatives or complementary actions.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool vs start_app_window_recording for browser/desktop-app debugging. Also explains manual-stop workflow vs duration, and mentions target aliases to aid selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Corvus400/video-capture-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server