Skip to main content
Glama

adb_batch_actions

Execute multiple Android input actions in one call to reduce ADB round-trips for multi-step UI interactions, with sequential execution and optional delays.

Instructions

Execute multiple input actions in a single tool call. Reduces ADB round-trips for multi-step UI interactions. Each action runs sequentially with an optional delay between them. Supported action types: tap, swipe, fling, long_press, double_tap, keyevent, text, drag, pinch, back, home, sleep.

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": {
      "actions": "<actions>"
    },
    "name": "adb_batch_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
actionsYesArray of actions to execute (1-50)
delayMsNoDelay between actions in ms (0-5000, default 100)
stopOnErrorNoStop execution if any action fails (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / actions / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / actions / items / properties / type / description
      Previous value: -"Action type"New value: +"Action type — one of: tap, swipe, fling, long_press, double_tap, keyevent, text, drag, pinch, back, home, sleep. The args field documents the expected argument format per type."
  3. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose useful behavior: sequential execution and an optional inter-action delay. It does not state what a failed batch returns, whether partial execution leaves the UI in a mutated state, or what the response looks like, which matters for a multi-step input tool with no safety annotations.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core purpose, then the benefit, then the execution semantics. The trailing enumeration of action types largely duplicates the schema enum, which is the only 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?

For a four-parameter mutation tool with no annotations and no output schema, the description covers purpose, sequencing, and action vocabulary well. It leaves the return value and failure/partial-execution semantics unexplained, which is the main gap for an agent deciding whether to batch a fragile UI flow.

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 every parameter (device, actions, delayMs, stopOnError) is documented inline with bounds and defaults, so the schema does the heavy lifting. The description adds only the sequencing concept ('optional delay between them'), which is already implied by delayMs; it adds no new meaning about the args string format.

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

Purpose4/5

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

The description uses a specific verb and resource ('Execute multiple input actions in a single tool call') and enumerates the supported action types, which lets an agent distinguish this batching tool from single-action siblings like adb_input or adb_input_text. It never names a sibling explicitly, so differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

'Reduces ADB round-trips for multi-step UI interactions' implies the use case (chained gestures) without ever saying when to prefer this over adb_input, adb_input_drag, or adb_tap_element. There are no exclusions and no prerequisites, so the agent must infer the selection rule.

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

Deploy Server

Other Tools