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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apps_beta_app_localizations_get_to_many_related

Retrieve beta app localization records for a specific App Store Connect app to view TestFlight feedback email, marketing URL, privacy policy, and locale details.

Instructions

GET /v1/apps/{id}/betaAppLocalizations (GET /v1/apps/{id}/betaAppLocalizations)

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": "apps_beta_app_localizations_get_to_many_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page
fields_betaAppLocalizationsNothe fields to include for returned resources of type betaAppLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it only implies a read via the 'GET' verb. It says nothing about pagination behavior, whether the response is a relationship linkage or full resources, rate limits, or authentication requirements.

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?

It is short, but the parentheses duplicate the identical path text, which is pure waste rather than genuine conciseness. Brevity here reflects under-specification, not efficient communication.

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 relationship-listing tool with three parameters, no annotations, and no output schema, the description supplies none of the context an agent needs — no explanation of the returned resource type, the parent/child relationship semantics, or pagination. It is effectively empty.

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 'id', 'limit', and 'fields_betaAppLocalizations' each documented in the schema, so the baseline of 3 applies. The description contributes no additional parameter meaning, such as that 'id' is the app id or what the field-selection enum returns.

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 the raw endpoint path duplicated verbatim, adding no information beyond the tool name 'apps_beta_app_localizations_get_to_many_related'. It does not say it lists the beta app localizations for an app, nor distinguishes it from sibling relationship endpoints such as apps_beta_app_localizations_get_to_many_relationship.

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 alternatives exist (e.g., beta_app_localizations_get_collection, the *_relationship variant), or any prerequisites. The agent is left to infer everything from the name.

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