Skip to main content
Glama
Sign In
MCP Appium

MCP Appium

Official
by appium
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

appium_perform_actions

Executes raw W3C Actions API sequences for custom multi-touch gestures, such as multi-finger rotations and edge swipes, and precise synchronized timing.

Instructions

Execute raw W3C Actions API sequences for advanced multi-touch gestures not covered by appium_gesture. Use this for custom multi-finger gestures (rotate, three-finger swipe, edge swipes), complex timing sequences, or any gesture requiring precise control over individual touch points. Prefer appium_gesture for standard gestures (tap, scroll, swipe, pinch) — it handles platform differences automatically.

Input Schema

NameRequiredDescriptionDefault
actionsYesW3C Actions API input source array. Each entry is one input source (pointer/key/none) with its action sequence. Multiple pointer sources enable multi-touch gestures (e.g. two-finger rotate, three-finger swipe). All sources execute in parallel, synchronized tick-by-tick.
sessionIdNoSession ID; defaults to the active session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.99.1
    • addedInput schema / properties / actions / items / additionalProperties
      Added value: +false
    • addedInput schema / properties / actions / items / properties / actions / items / additionalProperties
      Added value: +false
    • addedInput schema / properties / actions / items / properties / parameters / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv1.95.0
    • changedInput schema / properties / sessionId / description
      Previous value: -"Session ID to target. If omitted, uses the active session."New value: +"Session ID; defaults to the active session."
  3. First observedv1.92.11

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only mark readOnlyHint=false and openWorldHint=false, so the description must carry the interaction model — and it does, noting that multiple pointer sources run in parallel and are synchronized tick-by-tick, and that it is raw/low-level compared to the platform-normalizing sibling. It stops short of covering failure behavior (invalid action chains, element-level vs viewport coordinates, timeouts), which matters for a raw-action tool.

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?

Three sentences, each earning its place: capability, concrete use cases, then the routing rule to the alternative. Nothing is repeated from the schema and the highest-value guidance 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?

For a complex, highly-nested tool with no output schema, the description plus the fully documented schema give an agent what it needs to construct a valid call and choose the right tool. The remaining gap is expected failure/error semantics for malformed action chains, which is secondary given the schema quality.

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 the nested action structure (pointerType, origin, duration, button) is fully documented in the schema, so the baseline is 3. The description adds only the conceptual framing that individual sources correspond to fingers in multi-touch, not syntax or format detail beyond the schema.

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?

States a specific verb and resource — 'Execute raw W3C Actions API sequences' — and immediately scopes it against the sibling appium_gesture. An agent can distinguish this from the sibling without opening either schema, because the description names which gestures belong here (rotate, three-finger swipe, edge swipes) and which do not.

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

Usage Guidelines5/5

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

It gives both directions explicitly: use this for custom multi-finger gestures, complex timing, or precise per-touch-point control; prefer appium_gesture for standard gestures (tap, scroll, swipe, pinch). The alternative and the condition selecting it are named, plus a concrete reason (automatic platform handling).

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