Skip to main content
Glama

video_capture

Capture app screens, element positions, and scrollable content for launch video production. Pass routes to record multiple screens in video order, or omit routes to capture the current screen.

Instructions

Capture app screens for the launch video: screenshot, element positions and the full scroll content. Give routes to capture several screens in one call (in video order), or nothing to capture the current screen.

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_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoname for the current screen when routes is empty
routesNoexpo-router paths, e.g. ["/dashboard", "/analytics"]
scrollNocapture scroll content (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses what is captured, but says nothing about whether passing routes navigates the app and leaves it on the last screen, whether capture is synchronous, or what the returned data looks like — meaningful gaps for a tool that drives app navigation.

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: the first front-loads the purpose and output contents, the second covers the invocation branch. Little waste, though the parenthetical "(in video order)" could be folded into the clause about routes without loss.

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 3-parameter tool with no annotations and no output schema, the definition covers purpose and invocation but leaves the return payload shape and the app-state side effects of route navigation unexplained. Adequate to call it, insufficient to predict what happens after the call.

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?

With 100% schema description coverage, the baseline is 3. The description adds real meaning for routes by specifying video ordering of multi-screen capture and defining the empty case ("nothing" captures the current screen), but it never touches the name or scroll parameters beyond what the schema already documents.

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?

"Capture app screens for the launch video" names a specific verb and resource, and the follow-up enumerates what is captured (screenshot, element positions, full scroll content), which implicitly separates it from the plain app_screenshot sibling. It stops short of explicitly contrasting with app_screenshot, so an agent must infer which capture tool to reach for.

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?

"Give routes to capture several screens in one call (in video order), or nothing to capture the current screen" gives a clear branching rule for how to invoke the tool. It lacks explicit when-not guidance or a named alternative (e.g., versus app_screenshot or app_layout), so it is clear context rather than full routing guidance.

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