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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_store_version_experiment_treatments_get_instance

Retrieves details for a specific App Store version experiment treatment by ID, with optional included relationships and fields.

Instructions

GET /v1/appStoreVersionExperimentTreatments/{id} (GET /v1/appStoreVersionExperimentTreatments/{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_store_version_experiment_treatments_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appStoreVersionExperimentsNothe fields to include for returned resources of type appStoreVersionExperiments
fields_appStoreVersionExperimentTreatmentsNothe fields to include for returned resources of type appStoreVersionExperimentTreatments
limit_appStoreVersionExperimentTreatmentLocalizationsNomaximum number of related appStoreVersionExperimentTreatmentLocalizations returned (when they are included)
fields_appStoreVersionExperimentTreatmentLocalizationsNothe fields to include for returned resources of type appStoreVersionExperimentTreatmentLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.3/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 burden. The 'GET' prefix implies a read-only fetch, which is the only behavioral signal, but nothing is said about authentication requirements, pagination of related resources, or the include/fields query semantics.

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

Conciseness3/5

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

It is very short, but the content is a verbatim duplication of the path with the parenthetical repeat adding zero information. Brevity here reflects under-specification rather than efficient, front-loaded communication.

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 resource-fetch tool with six parameters, no annotations, and no output schema, the description provides nothing an agent needs beyond the raw path. It does not explain what the returned resource represents or how the include/fields options affect the response.

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% with 6 well-documented parameters (id, include, several fields_* and limit_* filters), so the schema already does the heavy lifting. The description adds nothing beyond the schema, which yields the baseline of 3.

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 repeats the REST endpoint path verbatim (and does so twice), which is a tautological restatement of the tool name 'app_store_version_experiment_treatments_get_instance'. It conveys that this retrieves a single experiment-treatment resource by id but adds no distinguishing detail versus the many sibling get_instance tools.

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 indication of when to use this versus alternatives such as app_store_version_experiment_treatments_localizations_get_to_many_related or the create/update/delete siblings. No prerequisites, context, or exclusions 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