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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_store_version_experiments_v2_update_instance

Update an App Store version experiment v2 instance by sending a PATCH request with the required JSON:API body to modify its configuration.

Instructions

PATCH /v2/appStoreVersionExperiments/{id} (PATCH /v2/appStoreVersionExperiments/{id}) Body shape: see OpenAPI components.schemas.AppStoreVersionExperimentV2UpdateRequest 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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "app_store_version_experiments_v2_update_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
bodyYesJSON body. Shape: components.schemas.AppStoreVersionExperimentV2UpdateRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.2/5.0
Behavior2/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 it discloses almost nothing. PATCH implies a partial update, but the description does not say which fields are mutable, whether omitted fields are preserved, whether changes are reversible, what permissions are required, or what happens to a running experiment. Only the body shape is hinted at via an OpenAPI schema reference the agent may not be able to resolve.

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 wasteful: the path '(PATCH /v2/appStoreVersionExperiments/{id})' is duplicated verbatim, and the opening line is not front-loaded with a human-readable purpose. The space is spent on redundant path text rather than useful information.

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 a nested JSON:API body, no annotations, and no output schema, the description is inadequate. It defers the entire body contract to an external OpenAPI components reference rather than summarizing the updatable fields, and gives no indication of the response or side effects.

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 both parameters (id, body) are documented in the schema, so the baseline is 3. The description adds only that the body follows the JSON:API envelope for AppStoreVersionExperimentV2UpdateRequest, which is marginally useful but does not go beyond the schema's own reference.

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 a restatement of the tool name as an HTTP path: 'PATCH /v2/appStoreVersionExperiments/{id}'. It conveys the verb (PATCH/update) and resource, but only in raw endpoint form and with no natural-language statement of what an update actually changes, and no differentiation from the v1 sibling app_store_version_experiments_update_instance. This is close to tautology.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention the v1 experiment update tool, nor any preconditions such as the experiment being in a draft/editable state, nor when a PATCH is appropriate over a create/delete.

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