MobAI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

uninstall_app

Uninstall an app from a mobile device by providing the device ID and the app's bundle ID (iOS) or package name (Android).

Instructions

Uninstall an app 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": {
      "device_id": "<device_id>",
      "bundle_id": "<bundle_id>"
    },
    "name": "uninstall_app"
  }
}

Input Schema

Name	Required	Description	Default
`device_id`	Yes	Device ID
`bundle_id`	Yes	App bundle ID (iOS) or package name (Android)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.1Jun 10, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, and the description lacks critical behavioral details such as side effects (data removal), required permissions, or confirmation prompts. The tool is destructive but reveals nothing else.

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?

Very concise single sentence with no unnecessary words. However, it may be too terse and could benefit from additional context without sacrificing brevity.

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 simple two-parameter tool with no output schema, the description is adequate but lacks important context about destructive nature and prerequisites.

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 100% with clear parameter descriptions, so the description adds no additional meaning. Baseline score is appropriate.

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

Purpose5/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 the target (app from device), which is specific and distinguishes from siblings like install_app or list_apps.

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?

No guidance on when to use this tool, prerequisites (e.g., app must be installed), or alternatives. However, the purpose is straightforward, making it minimally adequate.

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