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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

beta_app_localizations_get_collection

Retrieve beta app localizations from App Store Connect to manage localized TestFlight metadata, filter by app or locale, and include related app data.

Instructions

GET /v1/betaAppLocalizations (GET /v1/betaAppLocalizations)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "beta_app_localizations_get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
filter_appNofilter by id(s) of related 'app'
fields_appsNothe fields to include for returned resources of type apps
filter_localeNofilter by attribute 'locale'
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.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 behavioral burden, yet it discloses nothing: no auth requirements, no pagination behavior (despite a 'limit' param), no rate limits, no indication the result is a paginated collection. Repeating the URL adds zero behavioral context.

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 brevity is under-specification rather than conciseness: the parenthetical simply duplicates the path verbatim, so the single sentence earns nothing. There is no front-loaded purpose statement.

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 six-parameter collection endpoint with no annotations and no output schema, the description is essentially empty and leaves the agent to reconstruct intent from the tool name and schema alone. The rich schema partially compensates, but nothing about the resource or return shape is explained.

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 (limit, include, filter_app, fields_apps, filter_locale, fields_betaAppLocalizations) are documented in the schema itself. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 just the request path repeated twice: 'GET /v1/betaAppLocalizations (GET /v1/betaAppLocalizations)'. It restates the tool name and URL rather than stating in the description what the resource is or what the operation returns, which is the definition of a tautological purpose. An agent can only infer from the name that it lists beta app localizations.

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 whatsoever on when to use this collection endpoint versus siblings like beta_app_localizations_get_instance, beta_app_localizations_create_instance, or apps_beta_app_localizations_get_to_many_relationship. No conditions, prerequisites, or alternatives are mentioned.

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