Skip to main content
Glama
Sign In
appstore-connect-mcp

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Read] Get App Store version metadata

asc_metadata_get

Get localized App Store metadata (description, keywords, promotional text, what's new, support/marketing URLs) for an app version. Specify a locale or retrieve all locales.

Instructions

Read-only. Gets localized App Store metadata (description, keywords, promotional text, what's new, support URL, marketing URL) for a version. Locale must be explicit — returns all locales unless one is given.

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": {
      "appId": "<appId>",
      "version": "<version>"
    },
    "name": "asc_metadata_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id
localeNoOptional locale to filter to, e.g. "en-US"
versionYesApp Store version string, e.g. "1.1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It explicitly states 'Read-only' and discloses the locale behavior ('returns all locales unless one is given'), which is a valuable behavioral nuance. It does not mention authorization, rate limits, or error handling, but this is sufficient for a simple read operation.

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

Conciseness5/5

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

The description is two sentences, front-loaded with 'Read-only,' and every word adds value. It avoids restating schema details and efficiently conveys the core purpose and a key behavioral caveat.

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

Completeness4/5

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

For a read-only metadata getter, the description covers the resource, the fields returned, the read-only nature, and locale behavior. While there is no output schema, the listing of fields partially compensates; the exact response structure is not described, but this is not critical for a simple get operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters, so baseline is 3. The description adds meaningful context beyond the schema by explaining that locale is optional and that omitting it returns all locales, which is not obvious from the schema's 'Optional locale to filter to.'

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as 'localized App Store metadata' and lists specific fields (description, keywords, promotional text, what's new, support URL, marketing URL). It distinguishes this read tool from write siblings like asc_metadata_update by stating 'Read-only' and 'Gets... for a version.'

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

Usage Guidelines4/5

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

The read-only intent and target (a version's metadata) are clear, but it does not explicitly contrast with similar getters such as asc_version_get or asc_app_info_localization_get. No exclusion or alternative guidance is provided, but the usage context is unambiguous.

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