Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_custom_product_pages_create_instance

Creates an App Store custom product page in App Store Connect, enabling teams to add page variants for app marketing campaigns and promotions.

Instructions

POST /v1/appCustomProductPages (POST /v1/appCustomProductPages) Body shape: see OpenAPI components.schemas.AppCustomProductPageCreateRequest for the full JSON:API envelope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "app_custom_product_pages_create_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON body. Shape: components.schemas.AppCustomProductPageCreateRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden and delivers nothing. It does not state authentication scopes, whether the operation is idempotent, what side effects occur, or what is returned after the POST, despite being a mutation endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The snippet is short but its only content is duplicated verbatim in a redundant parenthetical, and it is under-specified rather than concise. Space that could carry purpose or body-shape context is spent on repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, this is far too thin. The description never hints at what the create request must contain (app relationship, name, visibility) or what the created resource looks like, leaving the agent dependent on an external OpenAPI reference it cannot resolve.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter (body) and schema description coverage is 100%, so the baseline is 3 per the rubric. The description's reference to components.schemas.AppCustomProductPageCreateRequest merely duplicates the schema's own description and points at an external document the agent cannot see, adding no real parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only echoes the HTTP route 'POST /v1/appCustomProductPages', which restates what the tool name already implies. It gives no natural-language statement of what an App Custom Product Page is or what creating one accomplishes, and it does nothing to separate this tool from siblings like app_custom_product_pages_update_instance or app_custom_product_page_versions_create_instance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, what prerequisites exist (e.g. an app ID must already exist), or how it relates to alternative creation tools. An agent gets no routing signal whatsoever.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools