podium-mcp

Overview Schema Source Related Servers Discussions Admin

tap_on

Tap, double-tap, or long-press screen elements by text, accessibility ID, or coordinates via Maestro flows. Requires bundle ID.

Instructions

Tap, double-tap, or long-press an element on screen via an ephemeral Maestro flow. Target by text (regex), accessibility id, or absolute x/y coordinates. bundleId is REQUIRED — Maestro needs it for the appId flow header. WebView caution: text/id selectors only resolve native accessibility nodes. Web-rendered elements inside WKWebView are invisible — tap_on will report COMPLETED but nothing is tapped. Use x+y coordinates instead for WebView content.

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": {
      "udid": "<udid>",
      "bundleId": "<bundleId>"
    },
    "name": "tap_on"
  }
}

Input Schema

Name	Required	Description
`udid`	Yes	Simulator / device UDID
`bundleId`	Yes	App bundle identifier (e.g. com.example.MyApp). Required by Maestro.
`text`	No	Element text or regex. Matches the FULL label/value case-insensitively (anchored ^…$); an invalid regex falls back to a substring match.
`id`	No	Accessibility ID of the element
`x`	No	X coordinate in logical points (numeric only; percent strings are not supported)
`y`	No	Y coordinate — required when x is provided
`double`	No	Use doubleTapOn instead of tapOn
`long`	No	Use longPressOn instead of tapOn
`longDurationMs`	No	Hold duration for long press in ms (max 10 000)
`index`	No	Zero-based index when multiple elements match
`timeoutMs`	No	Flow timeout in ms (default 30 000)
`noLaunch`	No	Skip the implicit launchApp attach step (default false). Set true when an open modal or navigation state must not be disturbed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries full behavioral disclosure. It reveals that WebView taps report COMPLETED without effect, explains the noLaunch param to avoid disturbing modals, and notes required bundleId. While it covers key traits, it could be more explicit about state requirements and return behavior.

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 a single, well-structured paragraph. It front-loads the main action and targeting methods, then adds critical warnings. Every sentence serves a purpose with no redundancy, achieving high efficiency.

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

Completeness4/5

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

Given no output schema, the description covers key aspects: action, targeting, required parameters, and a notable false-completion scenario. However, it lacks an explicit statement of return values or error handling, leaving a minor gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value beyond schema by explaining text matching behavior (anchored regex, fallback to substring), emphasizing bundleId necessity, and clarifying double/long press modes. This extra context raises the score.

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's function: tap, double-tap, or long-press on-screen elements via an ephemeral Maestro flow. It specifies targeting methods (text/regex, accessibility id, coordinates) and distinguishes from siblings by covering multiple tap modes.

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 provides explicit guidance: bundleId is required, and WebView content requires coordinates as text/id selectors fail. However, it does not directly compare to sibling tools like tap_with_fallback or swipe, leaving some usage context implicit.

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