Skip to main content
Glama

adb_build_and_install

Build a debug APK from an Android project and install it on the connected device, combining compilation and deployment in one step.

Instructions

Build a debug APK and install it on the connected device (convenience wrapper)

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": {
      "projectPath": "<projectPath>"
    },
    "name": "adb_build_and_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
timeoutNoBuild+install timeout in milliseconds (30s-30min, default 5min). V5 fix.
projectPathYesPath to the Android project root

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. Changed2 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / timeout
      Added value: +{
      +  "default": 300000,
      +  "description": "Build+install timeout in milliseconds (30s-30min, default 5min). V5 fix.",
      +  "maximum": 1800000,
      +  "minimum": 30000,
      +  "type": "integer"
      +}
  3. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It reveals the build variant (debug) and that it targets a connected device, but says nothing about whether an existing installed app is replaced or its data cleared, whether the build runs offline, what permissions or gradle state are required, or what the result reports on build failure versus install failure.

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 front-loaded sentence with no filler, stating the action and its scope. It is lean, but the brevity is partly the cause of the missing behavioral detail rather than a model of tightness.

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 three-parameter convenience tool with no output schema and no annotations, the description omits the two things an agent most needs: what the call returns (build output, APK path, install status) and the side effects of reinstalling over an existing app. Adequate but clearly incomplete.

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 projectPath, device serial, and the timeout range are already fully documented in the schema. The description adds no parameter-level meaning beyond that baseline.

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 states a concrete compound verb+resource: build a debug APK and install it on the connected device. An agent can distinguish it from adb_install (install only) and adb_gradle (arbitrary gradle task) without opening a schema, though neither sibling is named explicitly.

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 '(convenience wrapper)' implies this bundles build+install for the common single-device debug flow, which is weak when-to-use guidance. It does not say when to prefer adb_gradle plus adb_install separately, nor what prerequisites exist (connected device, gradle wrapper present).

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