Delete a specific App Clip default experience localization by providing its ID from the list call, removing unwanted localized content from your App Clip configuration.
Delete an App Clip default experience localization. [DELETE /v1/appClipDefaultExperienceLocalizations/{id}]
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID from the matching list call. |
Changes observed during successful MCP inspections.
v2.0.1Input schema / properties / id / descriptionAdded value: +"ID from the matching list call."v2.0.0Input schema / properties / id / descriptionRemoved value: -"Resource identifier."v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds no extra behavioral context beyond restating the delete operation, such as irreversibility, permissions, or side effects. No contradiction 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that states the purpose and includes the endpoint. No wasted words.
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 delete tool with one parameter and strong annotations, the description is adequate. It covers the essential operation and resource, though it could note that deletion is permanent, but this is implied by the destructiveHint annotation.
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?
The schema description for the only parameter, 'id', is 'ID from the matching list call,' which provides 100% coverage. The description itself does not add parameter details, but the baseline of 3 applies due to full schema coverage.
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?
The description clearly states the action ('Delete') and the specific resource ('App Clip default experience localization'), with the HTTP endpoint confirming the operation. This is a specific verb+resource pairing that distinguishes it from sibling tools like update, get, or create.
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 is provided on when to use this tool vs. alternatives, or any prerequisites/exclusions. The usage is only implied by the verb 'Delete' and the resource name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.