Skip to main content
Glama

record_browser_interaction

Capture real browser interactions with masked screenshots, cursor choreography, and frame timing, then export the recording as a local MP4 file.

Instructions

Record real browser interactions through continuously masked screenshots, cursor choreography and measured frame timing; exports local MP4.

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": {
      "url": "<url>",
      "output": "<output>"
    },
    "name": "record_browser_interaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
widthNo
heightNo
outputYes
recordNo
actionsNo
fullPageNo
recordFpsNo
showCursorNo
recordMaxSecondsNo
waitMillisecondsNo
allowInteractionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare a non-destructive, non-idempotent, closed-world write-ish operation; the description usefully adds that screenshots are continuously masked (a privacy behavior) and that timing is measured for export. However it omits the most consequential behavioral facts: that capture only happens when the 'record' flag is set, that page interactions are disabled unless explicitly allowed, and that recording is hard-capped at 30 seconds. Useful but incomplete beyond the annotations.

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?

A single dense sentence, front-loaded with the action and ending with the deliverable. Nothing is wasted, though the semicolon clause compresses two distinct ideas (capture mechanics and export) that could be split for scannability.

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

Completeness2/5

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

With 12 undocumented parameters, a nested action union, and no output-schema gap to excuse it, the description leaves far too much unexplained for a tool of this complexity. Critical gating flags (record, allowInteractions) and the 30-second cap are invisible to the caller.

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

Parameters2/5

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

Twelve parameters with 0% schema description coverage, and the description names none of them. The phrases 'cursor choreography' and 'measured frame timing' faintly gesture at showCursor and recordFps but give no defaults, ranges, or semantics for record, allowInteractions, actions, fullPage, or recordMaxSeconds, so the coverage gap is not compensated.

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: 'Record real browser interactions', plus the artifact produced ('exports local MP4'). It is clear what the tool does, but it draws no boundary against near-neighbors like capture_user_flow or capture_page, so the agent must infer when recording is the right choice.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and no named alternative among the many capture/export siblings. An agent gets the 'what' but nothing about selection or exclusions.

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