run-sequence-android-mcp

Overview Schema Source Related Servers Discussions Admin

Tap Element

android_tap_element

Taps a UI element by selector instead of coordinates for reliable interaction with dynamic layouts. Waits for the element to appear, then taps its center.

Instructions

Find a UI element by selector and tap its center. More reliable than coordinate taps for dynamic layouts. Waits for the element to appear (default 5s).

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

Input Schema

Name	Required	Description
`text`	No	Match by exact visible text
`index`	No	Which match to tap when multiple elements match (0-based). Defaults to 0.
`device`	No	Device id (serial or host:port). Optional -- when omitted, uses ANDROID_MCP_DEVICE env or auto-selects the connected device (physical devices preferred over emulators).
`timeout`	No	Max seconds to wait for the element. Defaults to 5.
`className`	No	Match by class name, e.g. 'android.widget.Button' or just 'Button'
`resourceId`	No	Match by resource id. Short ids like 'btn_login' are auto-expanded using the foreground app package
`contentDesc`	No	Match by accessibility label / content description (substring, case-insensitive)
`textContains`	No	Match by substring of visible text (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses waiting behavior (default 5s timeout) but does not explain failure behavior (e.g., exception on timeout, whether it scrolls, or if any side effects occur). For a tap action, this is adequate but could be more transparent.

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

Conciseness5/5

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

The description is two sentences long, front-loaded with the core action, and every sentence adds value. No unnecessary words or redundancy.

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?

The tool has 8 parameters but all are well-documented in the schema. The description does not explain selector priority (e.g., text vs resourceId) or return value. For a simple tap action, it is mostly complete but missing some context on selector combination logic.

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% and each parameter has a clear description. The description adds value by mentioning the default timeout, but otherwise does not provide additional parameter semantics beyond the schema. Baseline 3 applies.

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

Purpose5/5

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

The description clearly states the tool finds a UI element by selector and taps its center. It distinguishes from coordinate taps, which is a sibling tool (android_tap). The verb 'tap' and resource 'UI element' are specific.

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?

The description notes it is more reliable than coordinate taps for dynamic layouts and mentions waiting behavior (default 5s). It implies when to use, but does not explicitly state when not to use or name alternatives directly. Sibling android_tap exists but is not cross-referenced.

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