Skip to main content
Glama
clivejefferies

mobile-debug-mcp

swipe

Dispatch a swipe gesture on Android or iOS by providing start and end coordinates and duration. Optionally specify a device or platform.

Instructions

Purpose: Dispatch a swipe gesture on Android or iOS.

Inputs:

  • start and end coordinates

  • duration

  • platform/deviceId (optional)

Output Structure:

  • action_id, timestamp (ISO 8601), action_type

  • lifecycle_state: post-dispatch lifecycle state (pending_verification or failed)

  • source_module: runtime source of the action envelope

  • target.selector = { x1, y1, x2, y2, duration }

  • success = true when the swipe was dispatched

  • failure_code/retryable when dispatch fails

  • ui_fingerprint_before/ui_fingerprint_after when available

Recommended Usage:

  1. Determine swipe coordinates

  2. Call swipe

  3. If needed, wait for transition using wait_for_*

  4. Verify with expect_screen or expect_element_visible when a deterministic outcome is expected

Verification Guidance:

  • Swipe outcomes are less predictable; choose the most specific verifier available for the intended effect

  • Follow RESOLVE → ACT → WAIT (if needed) → EXPECT

  • Do not use wait_for_* alone as final verification when an applicable expect_* tool exists

Failure Handling:

  • TIMEOUT → retry once

  • UNKNOWN → capture a snapshot and stop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1YesStart X coordinate
x2YesEnd X coordinate
y1YesStart Y coordinate
y2YesEnd Y coordinate
deviceIdNoDevice Serial/UDID. Defaults to connected/booted device.
durationYesDuration in ms
platformNoPlatform to swipe on (android or ios)
Behavior5/5

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

Discloses output structure, lifecycle states, failure codes, and notes that swipe outcomes are less predictable. No annotations contradict.

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?

Well-structured with clear sections, front-loaded with purpose. Slightly long but every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers output structure, usage, verification, failure handling, and parameter details. Complete care for a 7-parameter tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input section adds context beyond 100% schema coverage, e.g., defaults for deviceId. Schema already detailed, but description adds value.

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?

Clearly states 'Dispatch a swipe gesture on Android or iOS.' Distinguishes from sibling tools like tap, scroll_to_element.

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?

Provides explicit 'Recommended Usage' steps, 'Verification Guidance' (e.g., Do not use wait_for_* alone), and 'Failure Handling' strategy.

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/clivejefferies/mobile-debug-tools'

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