Skip to main content
Glama

uninstall_app

Remove apps from Android devices by specifying their package names. This tool helps manage device storage and performance by uninstalling unwanted applications.

Instructions

Uninstall an app from the connected Android device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes

Implementation Reference

  • The handler function for the 'uninstall_app' tool. It takes a package_name string parameter and uses the 'adb uninstall' command to remove the app from the connected Android device, returning a success message or raising an error.
    @mcp.tool()
    def uninstall_app(package_name: str) -> str:
        """Uninstall an app from the connected Android device"""
        result = subprocess.run(["adb", "uninstall", package_name], capture_output=True, text=True)
        if result.returncode != 0:
            raise RuntimeError(f"Error uninstalling app '{package_name}': {result.stderr}")
        return f"App '{package_name}' has been uninstalled successfully."
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is 'uninstall,' implying a destructive mutation, but doesn't clarify if this requires specific permissions, is reversible, affects device performance, or has side effects. This leaves significant gaps for a tool that permanently removes software.

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?

The description is a single, clear sentence with no wasted words. It's front-loaded with the core action and target, making it highly efficient and easy to parse at a glance.

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?

Given the complexity (a destructive operation with no annotations, no output schema, and low schema coverage), the description is insufficient. It doesn't explain what 'uninstall' entails (e.g., removal of app and data), potential errors, or return values, leaving the agent with critical gaps in understanding the tool's behavior and outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description doesn't explicitly mention the 'package_name' parameter, but with only 1 parameter and 0% schema description coverage, it implicitly covers it by referring to 'an app.' This provides basic context, though it lacks details like format or examples. Since there are 0 parameters with schema descriptions, the baseline is 4, as the description compensates minimally.

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 clearly states the action ('uninstall') and target resource ('an app from the connected Android device'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'clear_app_data' or 'stop_app', which also affect apps but perform different operations, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an app installed first), exclusions (e.g., not for system apps), or compare to siblings like 'clear_app_data' (which removes data but keeps the app) or 'install_app' (the opposite action).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vs4vijay/espresso-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server