Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Uninstall App (IDB)

idb-uninstall
DestructiveIdempotent

Uninstall an iOS app by bundle ID, deleting its data and preferences for a clean reinstall. Automatically terminates the app if running and provides troubleshooting guidance for common failures.

Instructions

idb-uninstall

Uninstall application from iOS target - remove apps with complete data deletion for clean installs.

Overview

Removes installed applications by bundle ID with complete data and preferences deletion. Automatically terminates running apps before uninstall. Cannot remove system apps (user-installed only). Provides detailed error guidance for common failures (app not found, system app protection, uninstall errors).

Parameters

Required

  • bundleId (string): App bundle identifier to uninstall

Optional

  • udid (string): Target identifier - auto-detects if omitted

Returns

Uninstallation status with success indicator, bundle ID, command output, error details if failed, and troubleshooting guidance (app not found, system app protection, termination advice, alternative tools).

Examples

Uninstall app for clean reinstall

const result = await idbUninstallTool({
  bundleId: 'com.example.MyApp'
});

Uninstall from specific device

await idbUninstallTool({
  bundleId: 'com.example.MyApp',
  udid: 'DEVICE-UDID-123'
});

Related Tools

  • idb-install: Reinstall app after uninstall

  • idb-terminate: Stop app before uninstall (auto-handled)

  • idb-list-apps: Verify app is removed after uninstall

Notes

  • Removes app from target system completely

  • Deletes all app data and preferences

  • Automatically terminates app if running

  • Only user-installed apps can be uninstalled (system apps protected)

  • Clean install testing workflow: uninstall -> install -> test

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidNo
bundleIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds valuable behavioral context: complete data and preferences deletion, automatic termination of running apps, system app protection, and error guidance. This goes beyond what annotations provide, though it doesn't detail permission requirements or exact response format.

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?

The description is well-structured with clear sections (Overview, Parameters, Returns, Examples, Related Tools, Notes) and front-loads the core purpose. It's somewhat verbose with repeated information across Overview and Notes, but each section earns its place and the examples are useful.

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 2-parameter tool with no output schema, the description covers the essential context: what it does, parameters, return information, examples, and related tools. It could be more explicit about edge cases like invalid bundle IDs or device connection failures, but the error guidance mention covers common failures.

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 0%, so the description must compensate. It explains bundleId as the app bundle identifier to uninstall and udid as target identifier with auto-detection. This adds meaning beyond the bare schema, but the descriptions are minimal and don't provide format examples or constraints beyond what a developer would infer.

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 tool uninstalls applications from iOS targets by bundle ID with complete data deletion, distinguishing it from related tools like idb-install and simctl-uninstall. The verb 'uninstall' plus resource 'application from iOS target' is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (clean installs, removing user-installed apps) and notes that idb-terminate is auto-handled, idb-install is for reinstall, and idb-list-apps verifies removal. It doesn't explicitly state when NOT to use it versus simctl-uninstall, but the related tools section gives useful routing guidance.

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