Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Build/Test Details

xcodebuild-get-details
Read-onlyIdempotent

Retrieve detailed build and test logs from cached results to debug errors or warnings without overflowing context. Access full logs, filtered errors, or metadata on demand.

Instructions

xcodebuild-get-details

🔍 Retrieve detailed build or test output from cached results - Progressive disclosure for logs.

Provides on-demand access to full build and test logs that were cached during xcodebuild-build or xcodebuild-test execution. Implements progressive disclosure pattern: initial build/test responses return concise summaries to prevent token overflow, while this tool allows drilling down into full logs, filtered errors, warnings, or metadata when needed for debugging.

Advantages

• Access full build logs without cluttering initial responses • Filter to just errors or warnings for faster debugging • Retrieve exact command executed and exit code • Inspect build metadata and cache information

Parameters

Required

  • buildId (string): Cache ID from xcodebuild-build or xcodebuild-test response

  • detailType (string): Type of details to retrieve

    • "full-log": Complete stdout and stderr output

    • "errors-only": Lines containing errors or build failures

    • "warnings-only": Lines containing warnings

    • "summary": Build metadata and configuration used

    • "command": Exact xcodebuild command executed

    • "metadata": Cache info and output sizes

Optional

  • maxLines (number): Maximum lines to return (default: 100)

Returns

  • Tool execution results with requested build or test details

  • Full logs or filtered errors/warnings with line counts

  • Build metadata and execution information

Related Tools

  • xcodebuild-build: Build iOS projects (returns buildId)

  • xcodebuild-test: Run tests (returns testId)

  • simctl-get-details: Get simulator list details

Notes

  • Tool is auto-registered with MCP server

  • Requires valid cache ID from recent build/test

  • Cache IDs expire after 30 minutes

  • Use for debugging build failures and test issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buildIdYes
maxLinesNo
detailTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / buildId / description
      Removed value: -"Build ID from previous xcodebuild-build call"
    • removedInput schema / properties / detailType / description
      Removed value: -"Type of details to retrieve"
    • removedInput schema / properties / maxLines / description
      Removed value: -"Maximum number of lines to return for logs"
  2. First observedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds crucial behavioral context: progressive disclosure, cache ID requirement, 30-minute expiry, and line-count reporting. No contradictions with annotations.

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?

Well-structured with clear headers, bullet points, and front-loaded purpose. Every section adds value—parameters, returns, related tools, and notes—without redundancy or filler.

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?

Covers all aspects: purpose, usage, parameter semantics, return expectations, related tools, and caveats like cache expiry. For a tool with three parameters and six enum options, this description is complete and self-sufficient.

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?

Despite 0% schema description coverage, the description thoroughly documents each parameter, including the six enum values for detailType with meanings and the default for maxLines. This fully compensates for the schema's lack of descriptions.

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 states a specific action ('retrieve detailed build or test output') and resource ('cached results'), and clearly distinguishes itself from siblings like xcodebuild-build and simctl-get-details. The progressive disclosure pattern is explained upfront, making the tool's role unambiguous.

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

Usage Guidelines5/5

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

Explicitly states when to use (for debugging build failures and test issues) and when not to rely on the initial response. Lists related tools and notes cache expiry, giving clear context for selecting this tool over alternatives.

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