Skip to main content
Glama

start_app_window_recording

Record only the visible front-window region of a macOS app for debugging. Validates window visibility and supports manual-stop or timed recording.

Instructions

Start recording only the visible front-window region of a macOS app.

This is the first choice for Chrome, Safari, and desktop-app debugging. It
activates app_name, verifies the front window meets min_visible_ratio, then
records only that visible region via screencapture -R instead of recording
the full desktop.

Omit duration_seconds for the preferred manual-stop workflow, then call
stop_recording with the returned session_id. Options are forwarded to the
macOS backend after region is injected.

If visibility validation fails, the response is {"error": ..., "window": ...}
so the client can reposition or unminimize the target and retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_nameYesExact macOS application name (e.g. 'Google Chrome').
duration_secondsNoSeconds to record. Omit for manual-stop workflow.
output_pathNoAbsolute path. When omitted, defaults to default_output_root()/video_capture_<app_name>_window.mov.
paddingNoPixels added to the window region. Default 0.
min_visible_ratioNoMinimum visible_ratio. 0.0-1.0, default 0.8.
optionsNoForwarded to macOS backend (after region injection). Same keys as start_recording.options minus region.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description fully discloses behavior: activates app, verifies window visibility, records via screencapture -R, and returns error with window details on validation failure. No contradictions and no hidden side effects omitted.

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?

Eight sentences, ~90 words, front-loaded with core purpose. Every sentence adds essential information with no redundancy. Highly efficient.

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 purpose, use case, workflow, error handling. References sibling tool (stop_recording). Output schema exists but description explains error response. Slightly missing info on what happens if recording already exists, but acceptable given other strengths.

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%, so baseline is 3. Description adds workflow context for duration_seconds (manual vs timed) and explains options forwarding. This goes beyond raw schema descriptions.

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 clearly states the tool records only the visible front-window region of a macOS app, using specific verbs and resource. It distinguishes itself by noting it's the first choice for Chrome, Safari, and desktop-app debugging.

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?

Provides clear usage context: first choice for specific apps, workflow guidance (omit duration_seconds for manual-stop, then call stop_recording), and mentions error handling for visibility failures. Lacks explicit when-not-to-use but sufficiently guides correct invocation.

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