Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Uninstall App from Simulator

simctl-uninstall
DestructiveIdempotent

Uninstall iOS apps from a simulator by bundle ID to remove app data, preferences, and the app bundle, enabling clean testing and space management.

Instructions

simctl-uninstall

Uninstall iOS apps from simulators.

Overview

Removes an installed app from a simulator by its bundle ID. This cleans up all app data, preferences, and the app bundle itself from the simulator. Useful for clean testing, data removal, space management, and workflow automation.

Parameters

Required

  • udid (string): Simulator UDID (from simctl-list)

  • bundleId (string): App bundle ID (e.g., com.example.MyApp)

Returns

Uninstall status with bundle ID, simulator info (name, state, availability), success indicator, command output, and guidance for reinstallation or app management.

Examples

Uninstall app from simulator

await simctlUninstallTool({
  udid: 'ABC-123-DEF',
  bundleId: 'com.example.MyApp'
});

Clean install workflow

// Uninstall old version
await simctlUninstallTool({
  udid: 'TEST-DEVICE',
  bundleId: 'com.example.MyApp'
});
// Then reinstall
await simctlInstallTool({
  udid: 'TEST-DEVICE',
  appPath: '/path/to/MyApp.app'
});

Related Tools

  • simctl-install: Reinstall app after uninstall

  • simctl-list: Find simulator UDID

  • simctl-get-app-container: Check app container before uninstall

Notes

  • Bundle ID must follow format: com.company.appname

  • Removes app and all associated data/preferences

  • Validates simulator exists before attempting uninstall

  • Useful for clean testing workflows

  • Frees simulator disk space by removing unused apps

  • Test cycles requiring clean app installs benefit from uninstall automation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidYes
bundleIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark the tool as destructive and idempotent. The description adds meaningful behavioral detail beyond that: it specifies that all app data, preferences, and the bundle itself are removed, and that it validates simulator existence before uninstalling. No contradiction with annotations; it enriches the safety profile without repeating the hints.

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 lengthy but well-structured, with clear sections (Overview, Parameters, Returns, Examples, Related Tools, Notes) and the core purpose front-loaded. Every section earns its place – the examples and related tools are practical, and the notes are relevant. It could be tightened slightly (e.g., the Notes repeat some automation benefits), but overall it remains purposeful.

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

Completeness5/5

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

For a two-parameter, no-output-schema tool, this description is complete. It covers what the tool does, the parameters, the return value, usage examples, related tools, and important caveats (bundle ID format, data removal, simulator validation). Nothing an agent needs to call it correctly is missing.

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

Parameters5/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 – and it does thoroughly. The Parameters section explains udid as 'Simulator UDID (from simctl-list)' and bundleId with an example (com.example.MyApp). The Notes reinforce the bundle ID format. This adds real meaning beyond the bare schema property names.

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 opens with 'Uninstall iOS apps from simulators' and elaborates 'Removes an installed app from a simulator by its bundle ID.' This is a specific verb+resource statement that clearly distinguishes it from siblings like simctl-install (installation) and simctl-get-app-container (inspection). The purpose is 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 'Related Tools' section explicitly names simctl-install, simctl-list, and simctl-get-app-container, providing alternatives for adjacent tasks. It also gives usage scenarios ('clean testing, data removal, space management') and a clean-install workflow example. However, it stops short of explicit conditionals like 'use simctl-install when you need to install instead' – the guidance is present but not as crisply routed as it could be.

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