Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Launch App

mobile_launch_app

Opens a specified app on an iOS or Android device using its package name. Start apps by device identifier to automate mobile workflows and testing.

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.
localeNoComma-separated BCP 47 locale tags to launch the app with (e.g., fr-FR,en-GB)
packageNameYesThe package name of the app to launch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.0.53
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Comma-separated BCP 47 locale tags to launch the app with (e.g., fr-FR,en-GB)",
+  "type": "string"
+}
  3. Changed3 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / device
      Added value: +{
+  "description": "The device identifier to use. Use mobile_list_available_devices to find which devices are available to you.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "packageName"
-]New value: +[
+  "device",
+  "packageName"
+]
  4. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that: no statement about failure when the package is absent, whether the call blocks until the app is foregrounded, or how the optional locale affects the launched process.

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?

Three short sentences, front-loaded with the action and no padding. The first two sentences partially restate each other ('Launch an app...' / 'Use this to open a specific app'), which is the only real waste.

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?

For a low-complexity launch tool with full schema coverage and no output schema, this is close to sufficient. It still leaves the agent without guidance on the primary failure mode (app not installed) and on whether the launch is synchronous, which an agent orchestrating subsequent screen interactions would want to know.

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%, so all three parameters (device, locale, packageName) are already documented in the schema; the baseline is 3. The description reinforces where packageName comes from but adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Launch an app on mobile device') that an agent can act on immediately. It does not, however, explicitly differentiate itself from nearby siblings such as mobile_terminate_app or mobile_install_app beyond the obvious antonym/adjacency.

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?

It gives implied usage ('Use this to open a specific app') and a helpful pointer for sourcing the required package name, but offers no when-not guidance (e.g., what to do if the app is not installed, or when to use install vs launch). The referenced tool name 'list_apps_on_device' does not match the actual sibling 'mobile_list_apps', weakening the routing value.

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

Deploy Server

Other Tools