Cancel an inactive App Store phased release before rollout begins by deleting its phased release ID. Use it to stop a scheduled phased release configuration.
Cancel a phased release configuration before the phased release has started
| Name | Required | Description | Default |
|---|---|---|---|
| phasedReleaseId | Yes | Inactive App Store Version Phased Release ID |
Changes observed during successful MCP inspections.
v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations at all, the description must carry the full behavioral load. It discloses the key state constraint (must not have started) but says nothing about irreversibility, required App Store Connect permissions, or what happens to the parent version after cancellation — significant gaps for a destructive operation.
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?
One sentence, front-loaded with the verb/resource and then the constraint. Zero padding.
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?
For a simple one-parameter tool this covers the essentials of what and when, but with no annotations and no output schema the description should at least mention irreversibility or post-cancel behavior; those omissions leave it only minimally adequate.
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% and the single parameter is already documented as an "Inactive App Store Version Phased Release ID". The description adds no format, sourcing, or lookup guidance beyond the precondition already implied by the schema.
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?
States a specific verb (Cancel) plus the resource (a phased release configuration) and the state precondition. It is distinguishable from apple_update_phased_release / apple_create_phased_release by name and by the cancellation framing, though it does not explicitly name a sibling.
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?
"before the phased release has started" is an explicit precondition that gates usage and implicitly routes post-start cases to apple_update_phased_release. No alternative tool is named outright, so it stops short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.