adb-tv-mcp

Overview Schema Source Related Servers Discussions Admin

adb_uninstall

Uninstall any app from an Android TV or Android device by specifying its package name. Removes unwanted applications directly through ADB to free up storage and declutter your device.

Instructions

Uninstall an app by package 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": {
      "package": "<package>"
    },
    "name": "adb_uninstall"
  }
}

Input Schema

Name	Required	Description	Default
`serial`	No	device serial (host:port); omit if only one device
`package`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

C2.6/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 burden of behavioral disclosure. A mutation tool like uninstall should disclose that it permanently removes the app, potentially destroys user data, and cannot be undone, but none of this is stated. The single sentence is entirely silent on behavioral impact.

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?

One short sentence, zero waste, efficient. However, several dimensions are under-specified, so conciseness here reflects brevity more than quality that earned its place.

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?

A mutating tool with no annotations and no output schema, and the description provides minimal context. It doesn't mention what happens to app data, whether it prompts for confirmation, or whether it can be applied to system apps. Given the gravity of an uninstall operation, this is insufficient.

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 50% (package lacks a schema description). The description names the package parameter ('by package name'), confirming its semantics. The serial parameter's own schema description covers it, so the description adds modest value but doesn't exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb+resource ('Uninstall an app by package name'), which distinguishes it from install-oriented siblings like adb_install and list-oriented ones like adb_list_apps. However, it lacks differentiation from other device-management siblings (e.g., doesn't clarify that this is a mutating operation vs. read-only tools).

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 tool vs adb_install or adb_shell alternatives, nor any mention of prerequisites like needing app uninstall permissions or the package being uninstallable. The description does not give context for when this is appropriate beyond the obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.