Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next

Double Tap Screen

mobile_double_tap_on_screen
Destructive

Simulate a double-tap gesture at specific screen coordinates on mobile devices to trigger actions like opening apps, confirming selections, or activating UI elements during automated testing.

Instructions

Double-tap on the screen at given x,y coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
xYesThe x coordinate to double-tap, in pixels
yYesThe y coordinate to double-tap, in pixels

Implementation Reference

  • src/server.ts:356-370 (registration)
    Registration of the 'mobile_double_tap_on_screen' MCP tool, including input schema (device, x, y) and handler that calls doubleTap on the device-specific Robot instance.
    tool(
    	"mobile_double_tap_on_screen",
    	"Double Tap Screen",
    	"Double-tap on the screen at given x,y coordinates.",
    	{
    		device: z.string().describe("The device identifier to use. Use mobile_list_available_devices to find which devices are available to you."),
    		x: z.number().describe("The x coordinate to double-tap, in pixels"),
    		y: z.number().describe("The y coordinate to double-tap, in pixels"),
    	},
    	async ({ device, x, y }) => {
    		const robot = getRobotFromDevice(device);
    		await robot!.doubleTap(x, y);
    		return `Double-tapped on screen at coordinates: ${x}, ${y}`;
    	}
    );
  • The tool handler function for mobile_double_tap_on_screen, which retrieves the Robot for the device and invokes its doubleTap method.
    async ({ device, x, y }) => {
    	const robot = getRobotFromDevice(device);
    	await robot!.doubleTap(x, y);
    	return `Double-tapped on screen at coordinates: ${x}, ${y}`;
    }
  • AndroidRobot.doubleTap implementation: performs two taps at the coordinates with a 100ms delay between them.
    public async doubleTap(x: number, y: number): Promise<void> {
    	await this.tap(x, y);
    	await new Promise(r => setTimeout(r, 100)); // short delay
    	await this.tap(x, y);
    }
  • IosRobot.doubleTap implementation: delegates to WebDriverAgent (wda).doubleTap.
    public async doubleTap(x: number, y: number): Promise<void> {
    	const wda = await this.wda();
    	await wda.doubleTap(x, y);
    }
  • MobileDevice.doubleTap implementation (for simulators): performs two sequential taps.
    public async doubleTap(x: number, y: number): Promise<void> {
    	// TODO: should move into mobilecli itself as "io doubletap"
    	await this.tap(x, y);
    	await this.tap(x, y);
    }
Behavior3/5

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

Annotations provide destructiveHint=true, indicating potential side effects. The description adds context by specifying it's a double-tap action at coordinates, but doesn't elaborate on behavioral traits like whether it requires the screen to be active, if it triggers UI responses, or any rate limits. With annotations covering the destructive nature, the description adds minimal but relevant context.

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?

The description is a single, direct sentence with zero wasted words, front-loading the core action ('Double-tap on the screen') and essential details ('at given x,y coordinates'). It efficiently conveys the tool's purpose without 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?

Given a destructive tool with no output schema and full parameter coverage, the description adequately covers the basic action but lacks context on expected outcomes, error conditions, or interaction effects. It's minimal but functional for a simple gesture tool, though more behavioral detail would improve completeness.

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%, with clear documentation for device, x, and y parameters. The description adds no additional meaning beyond the schema, such as coordinate system details or device state requirements. Baseline 3 is appropriate since the schema fully documents parameters.

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?

The description clearly states the action ('double-tap') and target ('on the screen at given x,y coordinates'), distinguishing it from siblings like mobile_click_on_screen_at_coordinates (single tap) and mobile_long_press_on_screen_at_coordinates (long press). It specifies the exact gesture and location parameters.

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?

The description implies usage for double-tap interactions but doesn't explicitly state when to use this versus alternatives like single-tap or long-press tools. No guidance on prerequisites (e.g., device must be unlocked) or exclusions is provided, leaving usage context inferred rather than explicit.

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/mobile-next/mobile-mcp'

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