Skip to main content
Glama

video_capture_tap

Captures a screen interaction: records the current screen, animates a finger tap with a ripple on a chosen element, and records the resulting screen for use in app demo videos.

Instructions

Capture an interaction: the current screen, a tap on an element (animated finger + ripple in the video) and the screen it leads to.

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

Input Schema

NameRequiredDescriptionDefault
refNo
nameNoname for the screen before the tap
textNo
testIDNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 burden. It does disclose the visual output (animated finger, ripple, before/after screens), which is real value, but it never states whether this actually taps the live device or only renders an illustration, whether an existing recording session is required, how long it waits for the post-tap screen, or what happens if the tap target cannot be resolved.

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 well-formed sentence with the outcome front-loaded and no filler; the parenthetical about the finger and ripple earns its place by clarifying the artifact. It is compact but under-specified rather than padded.

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 four parameters, zero annotations, and no output schema, the description should cover element targeting and preconditions. It describes the result well but leaves an agent unable to determine from the text alone how to identify the element or whether a recording must already be running.

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?

Schema description coverage is only 25% (only 'name' is documented), so the description needed to compensate and does not. It refers to 'a tap on an element' without explaining that ref/text/testID are the three alternative element-locator parameters, nor how they interact or which takes precedence.

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?

Names a specific verb and resource and spells out the three-part sequence it produces: the current screen, an animated tap (finger + ripple), and the resulting screen. That is more informative than the bare name, though it never explicitly contrasts itself with the plain capture sibling (video_capture) or the plain tap sibling (app_tap).

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 only implied by the phrasing 'capture an interaction' – an agent can infer this is for producing video that shows a tap and its outcome, but there is no explicit when-to-use, no when-not-to-use, and no named alternative (e.g., 'use app_tap for a plain tap with no video').

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