mobilerun-mcp

Swipe

swipe

Simulate a touch gesture from (x1,y1) to (x2,y2) over a set duration to scroll, drag, or navigate mobile screens in agent-driven device control.

Instructions

Swipe from (x1, y1) to (x2, y2) over duration_ms / ms (default 300). mobilerun agent form: coordinate=[x, y], coordinate2=[x, y], duration in seconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "swipe"
  }
}

Input Schema

Name	Required	Description	Default
`ms`	No
`x1`	No
`x2`	No
`y1`	No
`y2`	No
`device`	No
`duration`	No
`coordinate`	No
`coordinate2`	No
`duration_ms`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose a concrete default (300 ms for the duration) and the unit semantics (seconds vs. ms), which is genuine added value, but it says nothing about return behavior, device targeting, or required permissions/state.

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?

Two short sentences, front-loaded with the coordinate semantics and the duration default. Slightly dense phrasing ('duration_ms / ms') but no wasted content.

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?

An output schema exists so return values need not be explained, and the description covers most of the 10 parameters. Gaps remain for the device parameter and for when to choose this gesture over scroll siblings, which for a 10-parameter tool is a noticeable omission.

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 0%, so the description must compensate, and it largely does: it maps x1/y1/x2/y2 to the drag path, documents the duration_ms/ms default of 300, and explains the coordinate=[x,y]/coordinate2=[x,y] alias form plus the seconds unit for duration. Only the device parameter is left unexplained.

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 names a specific gesture (swipe) and spells out its start/end coordinates, so an agent immediately knows what the tool does. It does not, however, distinguish itself from gesture siblings such as scroll, scroll_down, or tap, which perform overlapping drag-like actions.

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

Usage Guidelines2/5

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

There is no guidance on when to prefer swipe over scroll/scroll_down/scroll_until or tap-based interaction. Usage can only be inferred from the tool name, and no preconditions (e.g. screen must be settled) are stated.

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

Deploy Server