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_get_instance

Fetch a specific app custom product page by ID to view its name, URL, visibility, and related app or page versions for App Store Connect.

Instructions

GET /v1/appCustomProductPages/{id} (GET /v1/appCustomProductPages/{id})

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": {
      "id": "<id>"
    },
    "name": "app_custom_product_pages_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appsNothe fields to include for returned resources of type apps
fields_appCustomProductPagesNothe fields to include for returned resources of type appCustomProductPages
limit_appCustomProductPageVersionsNomaximum number of related appCustomProductPageVersions returned (when they are included)
fields_appCustomProductPageVersionsNothe fields to include for returned resources of type appCustomProductPageVersions

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 burden of behavioral disclosure, yet it offers nothing. It does not state that this is a read-only operation, does not describe error behavior for a missing id, does not mention auth requirements, and does not describe what is returned.

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 text is short but poorly structured: the same endpoint string is repeated verbatim in parentheses, which is pure noise, and there is no front-loaded purpose statement. Every word here is either redundant or uninformative.

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 GET-instance tool with no annotations and no output schema, the description should at minimum disclose that it is a safe read and describe the returned resource. It does neither, leaving the agent with only the schema-documented query parameters and a raw URL.

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?

Schema description coverage is 100% and all six parameters (id, include, fields_apps, fields_appCustomProductPages, limit_appCustomProductPageVersions, fields_appCustomProductPageVersions) are documented in the schema. The description adds no parameter meaning, but per the high-coverage baseline a 3 is appropriate.

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 is a bare restatement of the tool name as a URL path: 'GET /v1/appCustomProductPages/{id}', duplicated in parentheses. It conveys the verb and resource type but adds no meaningful explanation of what an 'app custom product page' instance retrieval is, and does nothing to distinguish this from the sibling app_custom_product_pages_update_instance or app_custom_product_pages_create_instance beyond the HTTP verb.

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 versus alternatives. No mention of the relationship variants (app_custom_product_pages_app_custom_product_page_versions_get_to_many_relationship) or the collection tool (app_custom_product_pages_get_collection), and no prerequisites or context are given.

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