mcp-android-emulator

long_press

Perform a long press at specified coordinates to trigger context menus on Android emulator.

Instructions

Perform a long press at the specified coordinates (useful for context menus)

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "long_press"
  }
}

Input Schema

Name	Required	Description
`x`	Yes	X coordinate
`y`	Yes	Y coordinate
`duration`	No	Duration in milliseconds (default: 1000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral disclosure. It explains the core action and the intended effect (context menus), but it does not disclose whether the operation is blocking, how duration is applied, or any side effects beyond the gesture. The schema covers duration, but the description adds minimal behavioral context.

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, front-loaded sentence with a helpful parenthetical. Every word earns its place, and the structure is immediately scannable.

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?

For a simple gesture tool with no output schema, the description plus schema adequately covers the action, parameters, and a typical use case. It could mention that duration is optional (schema already does), but it provides enough context for an agent to select and invoke the tool. The parenthetical about context menus adds completeness.

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?

The input schema already provides full descriptions for all three parameters (x, y, duration with default). The description merely rephrases 'at the specified coordinates,' adding no new semantic information beyond the schema. Baseline is 3 because coverage is 100%.

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 action ('Perform a long press') and the target ('at the specified coordinates'), plus a practical use case ('useful for context menus'). This distinguishes it from sibling tools like tap and double_tap.

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 parenthetical 'useful for context menus' provides a clear use context, but it does not explicitly name alternatives or exclusion criteria. It implies when to use long press (for context menus) but doesn't contrast with tap or other gestures.

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