Skip to main content
Glama

adb_input_pinch

Simulate pinch (zoom out) or spread (zoom in) gestures on Android via ADB. Supports swipe injection (universal) or sendevent (requires root) with configurable duration, angle, and steps.

Instructions

Perform a multi-touch pinch (zoom out) or spread (zoom in) gesture. Two fingers move symmetrically toward or away from a center point. Uses parallel swipe injection by default (universal, no root); when root is available, can use raw sendevent for true multi-touch MT protocol injection. The 'auto' method selects the best available approach.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cxYesCenter X coordinate of the pinch gesture
cyYesCenter Y coordinate of the pinch gesture
startRadiusYesStarting distance (px) from center to each finger
endRadiusYesEnding distance (px) from center to each finger. Smaller than startRadius = pinch/zoom-out, larger = spread/zoom-in
durationMsNoGesture duration in ms (100-5000, default 500)
angleNoAngle in degrees for the pinch axis (0=horizontal, 90=vertical, default 90)
stepsNoInterpolation steps for sendevent method (5-60, default 20). More steps = smoother gesture
methodNoInjection method: 'auto' (sendevent if root, else swipe), 'swipe' (parallel swipes, universal), 'sendevent' (raw MT protocol, requires root)auto
deviceNoDevice serial
Behavior3/5

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

No annotations exist, so the description must cover behavioral traits. It mentions method prerequisites (root for sendevent) and that swipe is universal. However, it omits potential limitations like device compatibility or failure modes.

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 very concise: three sentences covering purpose and method options. Front-loaded with the gesture type, it efficiently conveys the core functionality without unnecessary details.

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?

With 9 parameters and no output schema, the description provides the gesture concept but lacks information on return values, error handling, or expected outcomes. It is adequate but not fully complete for a complex tool.

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 coverage is 100% with detailed parameter descriptions. The description adds no extra parameter meaning beyond explaining the gesture and method selection, so baseline score 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 clearly states it performs a multi-touch pinch or spread gesture, specifying symmetrical finger movement. It distinguishes from sibling input tools like adb_input (general input) or adb_input_drag by focusing on a specific multi-touch gesture.

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 explains when to use swipe vs sendevent methods and that 'auto' selects the best approach. It doesn't explicitly state when not to use this tool (e.g., for single-touch gestures), but the specificity makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fullread/DeepADB'

If you have feedback or need assistance with the MCP directory API, please join our Discord server