Skip to main content
Glama

gesture-swipe

Simulate a swipe or drag gesture between two points on iOS simulators or Android emulators. Use to scroll content, dismiss modals, or drag elements in app testing.

Instructions

Execute a smooth swipe / drag touch gesture between two points on the device (iOS simulator or Android emulator). All from/to positions are normalized 0.0–1.0 (fractions of screen width/height, not pixels), same as gesture-tap. Generates interpolated Move events for a natural feel (~60fps). Swipe up (fromY > toY) to scroll content down. Use when you need to scroll a list, dismiss a modal, drag an element, or navigate between pages. Not supported on Chromium — use gesture-scroll there instead. Pass settle:true for a momentum-free swipe that lands exactly where the finger lifts (no fling), when you need a deterministic scroll distance. Returns { swiped: true, timestampMs }. Fails if the simulator-server / emulator backend is not reachable for the given device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toXYesEnd x: normalized 0.0–1.0 (not pixels; same as tap)
toYYesEnd y: normalized 0.0–1.0 (not pixels; same as tap)
udidYesTarget device id from `list-devices` (iOS UDID or Android serial).
fromXYesStart x: normalized 0.0–1.0 (not pixels; same as tap)
fromYYesStart y: normalized 0.0–1.0 (not pixels; same as tap)
settleNoMomentum-free swipe: decelerate into the end point (ease-out) so the OS reads ~0 release velocity and applies little to no fling. Use for scroll-to-element loops; default false (a natural flinging swipe).
durationMsNoTotal gesture duration in milliseconds (default 300)
Behavior5/5

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

Discloses normalized coordinates, ~60fps interpolation, swipe direction effect (fromY > toY scrolls down), settle parameter behavior (momentum-free), return value, and failure condition. No annotations provided, so description carries full burden and does it thoroughly.

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?

Description is concise yet comprehensive, with clear sections for purpose, usage, and parameter details. No unnecessary sentences; all information 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?

Given 7 parameters, no output schema, and no annotations, the description fully covers behavior, usage, parameter details, return value, and failure conditions. Complete for a mobile gesture tool.

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?

Schema coverage is 100%, but description adds value by explaining coordinate normalization, settle behavior, and direction semantics (e.g., 'Swipe up (fromY > toY) to scroll content down'). Adds context beyond 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?

Clearly states it executes a swipe/drag gesture on iOS/Android, with normalized coordinates. Distinguishes from siblings like gesture-tap and gesture-scroll by mentioning coordinate system similarity to gesture-tap and alternative for Chromium.

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?

Explicitly lists use cases (scroll list, dismiss modal, drag element, navigate pages) and exclusion ('Not supported on Chromium — use gesture-scroll there instead'). Provides clear guidance on when to use this tool.

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/software-mansion/argent'

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