Skip to main content
Glama

adb_start_activity

Launch an Android activity or app by specifying an intent or component name, optionally targeting a device serial.

Instructions

Start an activity or app by intent or component name

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": {
      "intent": "<intent>"
    },
    "name": "adb_start_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
intentYesIntent or component (e.g., 'com.example/.MainActivity' or '-a android.intent.action.VIEW -d https://example.com')

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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and discloses almost nothing: it does not say what happens on failure (e.g., activity not found), whether it brings an existing task to the foreground, or what the tool returns. For a device-mutating launch action this is a substantial gap.

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?

A single efficient sentence with the verb and mechanism front-loaded and no filler. It could still be lengthened slightly to add routing guidance without becoming bloated.

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 two-parameter, no-output, no-annotation tool the description is minimally viable, but an agent still lacks default-device behavior, expected return shape, and error semantics. Those gaps matter because nothing else in the definition supplies them.

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 coverage is 100%, with both parameters documented including a concrete example of the intent syntax, so the schema already does the work. The description only echoes the intent parameter and says nothing about what happens if device is omitted (default device?).

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 ("Start") and resource ("an activity or app") plus the mechanism ("by intent or component name"), so the action is unambiguous. It does not differentiate from close siblings like adb_start_app, adb_restart_app, or adb_open_url, which an agent must guess between.

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?

No guidance on when to use this versus adb_start_app or adb_open_url, and no mention of prerequisites such as the target device needing to be connected or the activity needing to exist. Usage must be inferred entirely from the one-line purpose.

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