Skip to main content
Glama

capture_user_flow

Execute explicitly authorized browser actions on a URL and capture the final real page state as output for reproducible UI evidence.

Instructions

Execute explicitly authorized bounded actions and capture the final real page state.

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

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.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, so the description's remaining job is to explain what actually happens. It hints that actions are limited and requires explicit authorization, but omits the hard bounds (max 30 actions, 5000ms waits, 30s recording cap), the interaction gate (allowInteractions defaults false), and what 'final real page state' returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but the compression costs too much meaning: 'bounded' and 'real page state' are unexplained jargon that an agent cannot operationalize.

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?

An output schema exists, so return values need not be described, but for a 12-parameter automation tool that mutates page state and can record video, one sentence leaves the agent unable to construct a valid call or understand the interaction-safety model.

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?

With 12 parameters at 0% schema description coverage, the burden falls entirely on the description, which says nothing about url, output path, viewport width/height, recording flags (record, recordFps, recordMaxSeconds), fullPage, showCursor, allowInteractions, or wait timing. Only 'actions' and 'bounded' loosely gestures at the actions array; everything else is undocumented in both places.

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

Purpose3/5

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

The verb phrase 'Execute ... actions and capture the final real page state' does convey a specific action-plus-capture operation, but it never names the resource (a web page/URL), never mentions user flows despite the tool name, and gives no signal distinguishing it from siblings like capture_page or analyze_user_flows.

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?

'Explicitly authorized bounded actions' hints at a prerequisite (authorization) but the description never says when to choose this over capture_page, nor when recording vs. plain capture applies. The agent must infer all routing decisions from the name alone.

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