Skip to main content
Glama

Launch App

mobile_launch_app
Destructive

Launch mobile apps on iOS or Android devices by specifying the package name, enabling automated app testing and interaction through the Mobile Next MCP server.

Instructions

Launch an app on mobile device. Use this to open a specific app. You can find the package name of the app by calling list_apps_on_device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
packageNameYesThe package name of the app to launch

Implementation Reference

  • src/server.ts:224-235 (registration)
    Registration of the mobile_launch_app tool, including schema definition and inline handler that validates input, requires a selected robot/device, calls robot.launchApp, and returns success message.
    tool(
    	"mobile_launch_app",
    	"Launch an app on mobile device. Use this to open a specific app. You can find the package name of the app by calling list_apps_on_device.",
    	{
    		packageName: z.string().describe("The package name of the app to launch"),
    	},
    	async ({ packageName }) => {
    		requireRobot();
    		await robot!.launchApp(packageName);
    		return `Launched app ${packageName}`;
    	}
    );
  • Inline handler function for mobile_launch_app tool: requires a device/robot to be selected, launches the app via robot.launchApp, returns confirmation.
    async ({ packageName }) => {
    	requireRobot();
    	await robot!.launchApp(packageName);
    	return `Launched app ${packageName}`;
    }
  • AndroidRobot.launchApp implementation: uses adb shell monkey to launch the app with LAUNCHER intent.
    public async launchApp(packageName: string): Promise<void> {
    	this.adb("shell", "monkey", "-p", packageName, "-c", "android.intent.category.LAUNCHER", "1");
    }
  • Simctl.launchApp (iPhone Simulator) implementation: uses xcrun simctl launch.
    public async launchApp(packageName: string) {
    	this.simctl("launch", this.simulatorUuid, packageName);
    }
  • IosRobot.launchApp implementation: asserts tunnel, uses go-ios launch command.
    public async launchApp(packageName: string): Promise<void> {
    	await this.assertTunnelRunning();
    	await this.ios("launch", packageName);
    }
Behavior3/5

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

The annotations include destructiveHint: true, which already indicates this is a potentially disruptive operation. The description adds context by specifying it's for launching apps on mobile devices, but doesn't elaborate on behavioral traits like whether it requires device permissions, if it affects other running apps, or any rate limits. With annotations covering the destructive nature, the description provides basic context but lacks richer behavioral details.

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 extremely concise and front-loaded: the first sentence states the core purpose, and the second provides essential usage guidance. Every sentence earns its place with no wasted words, making it easy for an AI agent to quickly understand the tool's function.

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?

Given the tool's moderate complexity (2 parameters, destructive operation) and the absence of an output schema, the description is reasonably complete. It covers the purpose, basic usage, and parameter context. However, it could be more comprehensive by addressing potential side effects or error conditions, especially since it's marked as destructive.

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 both parameters (device and packageName) fully documented in the schema. The description adds minimal value beyond the schema by mentioning that package names can be found via list_apps_on_device, but doesn't provide additional semantic context about parameter usage or constraints. This meets the baseline of 3 for high schema coverage.

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 clearly states the action ('Launch an app') and resource ('on mobile device'), making the purpose immediately understandable. It distinguishes itself from siblings like mobile_install_app and mobile_terminate_app by focusing on opening apps rather than installing or closing them. However, it doesn't explicitly contrast with mobile_open_url, which might also open apps via URLs.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: to open a specific app on a mobile device. It also offers guidance on prerequisites by mentioning that package names can be found using list_apps_on_device. However, it doesn't explicitly state when NOT to use it or name alternatives like mobile_open_url for URL-based app launching.

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/EmpathySlainLovers/MCP'

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