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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_store_version_phased_releases_create_instance

Create a phased release for an App Store version, enabling gradual rollout of an update to users instead of all at once.

Instructions

POST /v1/appStoreVersionPhasedReleases (POST /v1/appStoreVersionPhasedReleases) Body shape: see OpenAPI components.schemas.AppStoreVersionPhasedReleaseCreateRequest 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_store_version_phased_releases_create_instance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations, the description carries full burden but discloses nothing about permissions, side effects, idempotency, rate limits, or what fields the body must contain beyond a schema reference. It only indicates an HTTP method and path, which is insufficient.

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 description is short but includes a redundant duplication of the same endpoint in parentheses. It is not front-loaded with a useful purpose statement, and the repetition wastes space rather than clarifying.

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

Completeness1/5

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

For a create operation with nested body objects, no annotations, and no output schema, the description is severely lacking. It does not explain what a phased release is, what fields the body requires, what happens on success or failure, or any behavioral context needed to invoke the tool correctly.

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?

The input schema has 100% description coverage for the single body parameter, already documenting the JSON shape reference. The description merely repeats the schema reference, adding no additional semantic meaning. Baseline 3 applies when schema coverage is high.

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 essentially the HTTP route 'POST /v1/appStoreVersionPhasedReleases' repeated twice. It does not state in plain language what a phased release is or what creating one entails, and it fails to differentiate this tool from its siblings like app_store_version_phased_releases_update_instance or delete_instance. It restates the name rather than adding clarity.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives, what preconditions exist (e.g., an app store version must exist), or what the effect of creation is. The description is silent on usage context.

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