Modify a custom product page’s name or visibility by page ID to control how it appears in App Store listings.
Update a custom product page name or visibility
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | New name | |
| pageId | Yes | The custom product page ID | |
| visible | No | Whether the page is visible |
Changes observed during successful MCP inspections.
v0.2.1Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falsev0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose that this is not read-only, is open-world, non-idempotent, and destructive. The description adds only that name or visibility can be changed, but does not explain the destructive implications of changing visibility, permission requirements, or what happens to the page after the update.
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 redundant or wasted language. It is appropriately sized for the amount of information it chooses to convey.
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?
The annotations and complete parameter schema provide the essential context, and the description states the editable fields. However, for a destructive update tool with no output schema, it does not explain prerequisites, side effects of visibility changes, or expected results.
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 description coverage is 100%, so the schema already documents pageId, name, and visible. The description mentions name and visibility but does not add meaning beyond the schema, so the baseline of 3 is appropriate.
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: update a custom product page, limited to name or visibility. It is clear, but it does not explicitly differentiate this tool from siblings like create_custom_product_page, get_custom_product_page, or list_custom_product_pages.
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?
The description gives no guidance on when to use this tool versus alternatives such as get_custom_product_page or create_custom_product_page. Usage is only implied by the verb 'Update'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.