Skip to main content
Glama

Uninstall Adb Package

uninstall_adb_package
Destructive

Uninstalls a single package from an Android device via adb, removing its data for user 0. Use it to clean up or reset an app; missing packages return the device's own refusal reason.

Instructions

Uninstall one package from the device (adb uninstall), removing its data for user 0. A device-mutating tool; absent packages report the device's own refusal reason.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "emulator-5554",
      "package": "com.example.app"
    },
    "name": "uninstall_adb_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it
packageYesInstalled package to uninstall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: only user 0's data is removed, the call is device-mutating, and failures for absent packages surface the device's own refusal reason rather than a generic error.

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, no padding, with the destructive scope of the operation stated up front before the error-behaviour note. Every clause carries information.

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

Completeness4/5

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

For a two-parameter mutation tool with no output schema, the description covers the essential behavioural facts, including what gets removed and how failures are reported. It could still note permission prerequisites or whether the package must be stopped first, but nothing critical is missing.

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% and both parameters already carry precise descriptions (serial format, package pattern), so the baseline of 3 applies. The description only reinforces the single-package constraint and adds nothing about serial or package syntax.

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?

It states a specific verb and resource ("Uninstall one package from the device") and pins the underlying mechanism to `adb uninstall`, which cleanly separates it from install_adb_package or inspect_adb_package. It never names a sibling or states an explicit alternative, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "one package" implies the scope of a call and the tool name makes its purpose evident, but there is no explicit when-to-use guidance, no prerequisites (device authorisation, debug mode), and no pointer to install_adb_package for the reverse operation. Usage is only implied.

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