Skip to main content
Glama

video_record

Records live phone-screen clips of an Expo app, with optional route navigation, smooth scrolling, or mid-recording taps to capture real interactions.

Instructions

Screen-record the phone for a few seconds (real frames, ~6-12 fps): optionally navigate first, scroll smoothly, or tap an element mid-way. The clip plays in the video as a live recording.

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

Input Schema

NameRequiredDescriptionDefault
tapNovisible text of an element to tap mid-recording
nameNo
routeNopage to open; the opening (loading, entrance animations) is recorded live
tapAtNosecond at which to tap (default: halfway)
scrollNoscroll smoothly while recording (true, or distance in dp)
secondsNo1-15, default 4
liveLoadNorecord the page opening (default true when route is given)
scrollFromNowhen scrolling starts, as a fraction of the recording (default 0.5 with route: hold while the page loads)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: ~6-12 fps, a few-second duration, real frames, and that the clip is embedded as a live recording. It omits where the recording is stored, what is returned, and any device permission or setup implications for an 8-parameter recording tool.

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?

Two sentences, front-loaded with the core action and frame-rate context, followed by the optional behaviors. No redundant restatement of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters, no annotations, and no output schema, the description covers behavior well but leaves the delivery of the result (file location, returned handle, failure modes) undocumented, which an agent would need before relying on the output.

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 already 88%, so the baseline is 3, but the description adds real semantic value by showing how route, scroll, and tap compose into a single recording (navigate first, then scroll, tap mid-way) rather than as isolated flags.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('screen-record the phone') and enumerates the three optional behaviors (navigate, scroll, tap) that define the tool. It does not distinguish itself from siblings like video_capture or video_capture_tap, so an agent must still infer when this differs from those.

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?

Usage is implied through the optional modes ('optionally navigate first, scroll smoothly, or tap an element mid-way'), which tells an agent what can be combined, but there is no explicit when-to-use or when-not-to-use guidance relative to the other video_* tools.

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