Create an App Clip advanced experience image for App Store Connect by submitting a request with fileName and fileSize.
Create an App Clip advanced experience image. [POST /v1/appClipAdvancedExperienceImages]
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON:API request body (Apple schema: AppClipAdvancedExperienceImageCreateRequest). |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description merely repeats the creation action already implied by the tool name and annotations (readOnlyHint=false). It does not disclose any additional behavioral traits, such as whether the image file must be uploaded separately, size limits, or other side effects.
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 sentence plus the endpoint reference, which is front-loaded with the purpose. There is no extraneous information; every word earns its place.
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?
Given the nested schema (with required attributes) and lack of output schema, the description is incomplete. It does not explain what the tool returns, any prerequisites (e.g., image upload), or how this relates to other advanced experience tools.
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%, so the input schema fully documents the required parameters. The description does not add any parameter-specific details beyond what is already in the schema, resulting in no added value.
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 ('Create') and the resource ('App Clip advanced experience image'), and includes the HTTP method and endpoint for additional context. It distinguishes itself from siblings like get and update for the same resource.
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 versus alternatives, such as when to create an image vs. the parent advanced experience. No prerequisites or context for invocation are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.