Enable a capability type for a specific App Store Connect bundle ID, with optional settings, to configure app services such as iCloud or push notifications.
Enable a capability for a bundle ID
| Name | Required | Description | Default |
|---|---|---|---|
| settings | No | Optional capability settings | |
| bundleIdId | Yes | The ID of the bundle ID | |
| capabilityType | Yes | The type of capability to enable |
Changes observed during successful MCP inspections.
v1.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Enable', which implies mutation, but does not mention permissions, side effects, reversibility, or success/failure indicators. This is insufficient for safe agent invocations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence. Every word is necessary, and it is efficiently front-loaded without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite low complexity (3 params, no output schema), the description lacks information about return values, error handling, or the relationship with sibling tools like 'disable_bundle_capability'. It is incomplete for practical use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all parameters. The description adds no extra meaning beyond what the schema provides (e.g., for 'capabilityType' the enum values are already listed). Baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool's action ('Enable') and resource ('capability for a bundle ID'). It directly distinguishes from the sibling 'disable_bundle_capability'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives. There is a sibling 'disable_bundle_capability', but the description does not specify prerequisites or context for enabling capabilities.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.