@wilsonbeam/openclaw-adb-mcp

Overview Schema Source Related Servers Discussions Admin

adb_long_press

Perform a long press at specified screen coordinates on an Android device via ADB, with optional duration and device targeting.

Instructions

Long press on the screen at the specified coordinates

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

Input Schema

Name	Required	Description
`x`	Yes	X coordinate
`y`	Yes	Y coordinate
`deviceId`	No	Target device ID (optional)
`durationMs`	No	Duration in milliseconds (default 1000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure. It only describes the action itself and doesn't mention behavior such as press duration release, possible context menu triggers, or prerequisites like device connection; this is insufficient for a simulated touch action.

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?

One sentence, direct and to the point; no unnecessary words, and the key information is front-loaded.

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?

The schema fully documents parameters including the default duration, and the action is simple enough that the description adequately conveys the tool's purpose; however, it could benefit from mentioning the press-release behavior.

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?

All four parameters are fully described in the schema (100% coverage), and the description adds no more than restating 'coordinates', so the baseline of 3 is appropriate.

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 uses a clear verb 'Long press' and specifies the target resource 'screen' with coordinates, effectively distinguishing it from sibling tools like adb_tap and adb_swipe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives; the description simply states the action without mentioning that adb_tap or adb_swipe are alternatives for different gestures.

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