Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next

Uninstall App

mobile_uninstall_app
Destructive

Remove applications from iOS or Android mobile devices by specifying the device identifier and app bundle ID or package name.

Instructions

Uninstall an app from mobile device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
bundle_idYesBundle identifier (iOS) or package name (Android) of the app to be uninstalled

Implementation Reference

  • src/server.ts:311-324 (registration)
    Registration of the 'mobile_uninstall_app' tool, including input schema (device, bundle_id) and handler that delegates to the appropriate Robot's uninstallApp method
    tool(
    	"mobile_uninstall_app",
    	"Uninstall App",
    	"Uninstall an app from mobile device",
    	{
    		device: z.string().describe("The device identifier to use. Use mobile_list_available_devices to find which devices are available to you."),
    		bundle_id: z.string().describe("Bundle identifier (iOS) or package name (Android) of the app to be uninstalled"),
    	},
    	async ({ device, bundle_id }) => {
    		const robot = getRobotFromDevice(device);
    		await robot.uninstallApp(bundle_id);
    		return `Uninstalled app ${bundle_id}`;
    	}
    );
  • Implementation of uninstallApp in AndroidRobot using adb uninstall command
    public async uninstallApp(bundleId: string): Promise<void> {
    	try {
    		this.adb("uninstall", bundleId);
    	} catch (error: any) {
    		const stdout = error.stdout ? error.stdout.toString() : "";
    		const stderr = error.stderr ? error.stderr.toString() : "";
    		const output = (stdout + stderr).trim();
    		throw new ActionableError(output || error.message);
    	}
    }
  • Implementation of uninstallApp in IosRobot using go-ios uninstall command
    public async uninstallApp(bundleId: string): Promise<void> {
    	await this.assertTunnelRunning();
    	try {
    		await this.ios("uninstall", "--bundleid", bundleId);
    	} catch (error: any) {
    		const stdout = error.stdout ? error.stdout.toString() : "";
    		const stderr = error.stderr ? error.stderr.toString() : "";
    		const output = (stdout + stderr).trim();
    		throw new ActionableError(output || error.message);
    	}
    }
  • Implementation of uninstallApp in MobileDevice (for simulators) using mobilecli apps uninstall command
    public async uninstallApp(bundleId: string): Promise<void> {
    	this.runCommand(["apps", "uninstall", bundleId]);
    }
Behavior3/5

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

The annotations include destructiveHint=true, indicating a destructive operation, which the description aligns with by stating 'uninstall' (a destructive action). However, the description adds minimal behavioral context beyond this—it doesn't specify if uninstallation is permanent, requires specific permissions, or has side effects like data loss. With annotations covering the destructive nature, the description adds some value but lacks depth on behavioral traits.

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, efficient sentence that directly states the tool's purpose without redundancy. It's front-loaded with the core action and resource, making it easy to parse quickly. There's no wasted language, and it earns its place by clearly conveying the essential function.

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?

Given the tool's complexity (destructive operation with 2 parameters), the description is minimal but adequate when combined with annotations and schema. It lacks output details (no output schema provided) and doesn't cover error cases or success conditions. However, with annotations indicating destructiveness and full schema coverage, it meets a basic threshold but leaves gaps in behavioral context.

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?

The input schema has 100% description coverage, with clear documentation for both parameters (device and bundle_id). The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to given the schema's completeness.

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 ('app from mobile device'), which is specific and unambiguous. It distinguishes from siblings like mobile_install_app and mobile_terminate_app by specifying removal rather than installation or temporary termination. However, it doesn't explicitly mention permanent removal versus temporary actions, which slightly limits differentiation.

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 device availability from mobile_list_available_devices, though hinted in schema), exclusions (e.g., not for system apps), or comparisons to siblings like mobile_terminate_app (which stops but doesn't remove). This leaves the agent without contextual usage direction.

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/mobile-next/mobile-mcp'

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