Skip to main content
Glama

adb_start_app

Launch an Android app by package name, resolving and starting its default launcher activity on a specified device.

Instructions

Launch an app by package name (resolves and starts the default launcher activity)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "packageName": "<packageName>"
    },
    "name": "adb_start_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
packageNameYesPackage name (e.g., 'com.example.app')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.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 changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose genuine behavior beyond the schema: the tool performs launcher-intent resolution instead of starting a named activity. However, it is silent on failure modes (package not installed, no launcher activity, app already running) and on what the call returns.

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?

A single front-loaded sentence with the core action first and the clarifying resolution detail in a parenthetical. No padding or redundant restatement of the name.

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 simple two-parameter launch tool with no output schema and full schema documentation, the description covers what the tool does and how it resolves the activity. It stops short of the operational details an agent would want, such as preconditions or expected result on failure.

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%, including an example package name and the device serial, so the schema already does the parameter work. The description only restates that the package name is the key input and adds no format, targeting, or device-selection detail.

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 by package name') and adds the resolution mechanism ('resolves and starts the default launcher activity'), which implicitly separates it from adb_start_activity. It does not name any sibling explicitly, so an agent must still infer the boundary with adb_start_activity and adb_restart_app.

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 parenthetical implies the intended case (you know the package but not the concrete activity), but there is no explicit when-to-use/when-not guidance and no mention of adb_start_activity, adb_restart_app, or adb_open_url as alternatives. Usage is implied rather than stated.

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