Skip to main content
Glama

adb_install

Install an APK on a connected Android device using its full local file path, with options to replace an existing app or allow a version downgrade.

Instructions

Install an APK on the device. Provide the full local path to the APK file.

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": {
      "apkPath": "<apkPath>"
    },
    "name": "adb_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
apkPathYesLocal filesystem path to the APK file
replaceNoReplace existing app (-r flag)
downgradeNoAllow version downgrade (-d flag)

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

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only implies a device-mutating installation. It omits useful operational context such as replacement being enabled by default, downgrade behavior, multi-device targeting, and what success or failure looks like.

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?

Two short sentences front-load the operation and then state the required input. There is no redundant or irrelevant wording.

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 four-parameter install command with a fully documented input schema, this is sufficient for the basic invocation. Missing sibling-selection guidance and behavioral or result context remain notable because neither annotations nor an output schema fill those gaps.

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 the baseline of 3 applies. The description reinforces that apkPath must be a full local path but adds nothing beyond the schema for device, replace, or downgrade.

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 uses a specific verb and resource—"Install an APK on the device"—so the operation and target are immediately clear. It does not explicitly distinguish this local-APK installer from siblings such as adb_build_and_install, adb_install_bundle, or adb_multi_install.

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 full-local-path instruction establishes a basic precondition and implies use when an APK is already available locally. It gives no explicit routing guidance for build-and-install, bundle, market, or multi-device alternatives, and does not explain when the optional device parameter is needed.

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