Skip to main content
Glama

adb_uninstall

Removes an Android app package from a connected device via ADB, with an option to keep app data and cache when uninstalling.

Instructions

Uninstall a package from the device

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_uninstall"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
keepDataNoKeep app data and cache (-k flag)
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

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 behavioral burden and discloses almost nothing. It does not say the operation is destructive and generally irreversible without a reinstall, that app data is destroyed by default unless keepData is set, or that uninstalling system/privileged packages may fail or require root.

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 zero filler, so structure is good. It is arguably under-specified rather than over-long, but nothing in it wastes space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive mutation tool with no annotations and no output schema, so the description should warn about irreversibility, data loss, and likely failure modes for system packages. None of that is present, leaving the agent under-informed for a risky operation.

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 every parameter including the keepData '-k flag' and device serial is already documented in the schema. The description adds no meaning beyond it, which lands at the baseline 3 for a fully covered 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 ('Uninstall a package from the device'), which cleanly separates it from adb_install, adb_clear_data and adb_multi_install. It never names those siblings or the device scope explicitly, so it stops short of a 5.

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?

There is no when-to-use guidance, no stated prerequisites (device serial required, USB/TCP connection must exist), and no pointer to alternatives such as adb_clear_data for wiping data only or adb_multi_install for bulk package handling. The agent must infer all routing from the tool name.

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