Skip to main content
Glama

Record screen

record_screen
Destructive

Use this when the task calls for a short bounded screen recording when motion/timing is necessary to diagnose a UI issue. Prefer screenshot_region for static visual verification because it is cheaper and easier to inspect.

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": {
      "device": "<device>"
    },
    "name": "record_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo1..60.
deviceYesReMCP device id returned by list_devices. Required for every device operation.
destinationNoPermitted output path. Omit the extension to accept the native format. GNOME may produce .webm or .mp4; other backends produce .mp4. An explicit extension must match the recorded format.
duration_secondsNo1..120 seconds.

Output Schema

NameRequiredDescriptionDefault
dataNoRecord screen structured result for record_screen. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload.
textYesConcise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / destination / description
      Previous value: -"Permitted output path. If an extension is supplied, use .webm for native GNOME Wayland recording and .mp4 for the other recorder backends."New value: +"Permitted output path. Omit the extension to accept the native format. GNOME may produce .webm or .mp4; other backends produce .mp4. An explicit extension must match the recorded format."
  2. Added
  3. Removed
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description needs to say what gets destroyed; it does not mention that writing to destination may overwrite an existing file, nor any duration/cost implications of long captures. It does add a useful relative-cost framing versus screenshot_region, which is real value beyond the annotation block.

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?

Two tight sentences with the usage condition front-loaded and no filler. The phrasing doubles up awkwardly ('when the task calls for ... when motion/timing'), and no sentence tells the agent what the tool actually produces.

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?

An output schema exists, so return values need not be explained, and the annotations carry the safety profile. What is missing is the overwrite/artifact behavior of a destructive write, which matters for a tool flagged destructiveHint=true.

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 100%, so device, fps, duration_seconds, and destination formats are already fully documented in the schema. The description adds no parameter-level meaning such as default fps or how destination behaves when omitted, so the baseline 3 applies.

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?

The description identifies a screen-recording tool scoped to short, bounded captures used for diagnosing motion/timing UI issues, which distinguishes it from snapshot-style siblings. It never states plainly that the output is a recording file written to a destination path, leaving the concrete artifact implicit.

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?

Both directions are explicit: use this when motion or timing must be observed, and prefer screenshot_region for static visual verification. The reason (cheaper, easier to inspect) is given, so the agent can route between the two without opening either schema.

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