Delete a custom product page to disable its campaign URL and stop outdated App Store content from being served.
Delete a custom product page; its URL stops working in campaigns
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes |
Changes observed during successful MCP inspections.
v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully states that the page URL stops working in campaigns, but does not disclose irreversibility, permission requirements, or what happens to associated localizations and campaign references.
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 with no wasted words. The consequence is appended efficiently via a semicolon.
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 destructive tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. It covers the basic consequence but omits irreversibility, side effects on localizations, and any confirmation or prerequisite context.
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 has one required parameter, pageId, with 0% description coverage, and the description never mentions it. The single sentence implies the target is the page, but adds no format, source, or identifier guidance beyond what the schema already provides.
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 states a specific verb and resource: deleting a custom product page. It is distinguishable from sibling update/get/list custom product page tools, though it does not explicitly distinguish itself from deletion tools for related resources such as localizations.
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?
Usage is implied by the name and description: use this to remove a custom product page. There is no explicit guidance on when not to use it, prerequisites, or how it differs from related deletion tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.