Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

idb-list-apps

Discover which iOS apps are installed and running on a device or simulator. Filter by install type (user, system, internal) or focus on active processes. Get structured JSON metadata to identify test targets and automate actions.

Instructions

idb-list-apps

List installed applications - discover apps available for testing with bundle IDs and running status.

Overview

Enumerates all installed applications on iOS targets with structured metadata including bundle ID, app name, install type (system/user/internal), running status, debuggability, and architecture. Filters apps by install type or running status to focus on user apps or active processes. Parses IDB's pipe-separated output into structured JSON for easy programmatic access.

Parameters

Required

None - all parameters are optional

Optional

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

  • filterType (string): Filter by install type ("system", "user", or "internal")

  • runningOnly (boolean): Show only currently running apps

Returns

Structured app list with summary counts (total, running, debuggable, by install type), separate arrays for running vs. installed apps, applied filter details, and actionable guidance for launching, terminating, installing, or debugging apps.

Examples

List user-installed apps to find test target

const result = await idbListAppsTool({
  filterType: 'user'
});

Find running app for UI automation

const running = await idbListAppsTool({ runningOnly: true });

List all apps on specific device

const all = await idbListAppsTool({
  udid: 'DEVICE-UDID-123'
});

Related Tools

  • idb-launch: Launch app by bundle ID discovered here

  • idb-terminate: Stop running app found in list

  • idb-install: Install new app to target

Notes

  • IDB outputs pipe-separated text, converted to structured JSON

  • Output format: bundle_id | app_name | install_type | arch | running | debuggable

  • Filter by install type to focus on user apps vs system apps

  • Running status helps identify active processes for UI automation

  • Debuggable status indicates if debugger can be attached

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
udidNo
filterTypeNo
runningOnlyNo

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations, the description fully discloses behaviors: enumerates all installed apps, provides structured metadata, converts pipe-separated output to JSON, and indicates auto-detection of UDID. Does not contradict any annotations.

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?

Structured with clear headings and front-loaded summary. Some redundancy (Returns repeats details from Overview) but each section adds value. Could be slightly more concise.

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?

Given no output schema and 3 parameters, the description covers return format (summary counts, arrays), provides examples, and notes about IDB output format. Leaves no major gaps for an agent to use the tool correctly.

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?

Schema coverage is 0%, but the description's Parameters section explains each parameter: udid (auto-detects), filterType (enum values listed), runningOnly (boolean for running apps). Adds meaning beyond the bare schema.

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 explicitly states 'List installed applications' and distinguishes it by mentioning 'discover apps available for testing with bundle IDs and running status.' Among siblings like idb-targets, simctl-list, and idb-launch, this tool uniquely focuses on enumerating installed apps.

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?

Provides guidance on filtering by install type or running status, and the Related Tools section suggests when to use this tool in conjunction with launching, terminating, or installing apps. However, lacks explicit when-not or alternative comparisons.

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/conorluddy/xc-mcp'

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