Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by Fourni-j
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_app_metadata

Retrieve localized app metadata including title, subtitle, keywords, description, and promotional text for all locales to support ASO review. Requires app ID from list_apps.

Instructions

Get localized metadata for an app: title, subtitle, keywords, description, and promotional text for all locales. Useful for ASO review. Requires appId from list_apps.

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>"
    },
    "name": "get_app_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp Store Connect app ID (from list_apps)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Does not disclose whether tool is read-only, idempotent, requires authentication, or has rate limits. Only implies a read operation through naming and description.

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?

Two sentences contain all essential information: purpose, fields, use case, and prerequisite. No extraneous text.

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?

With one parameter and no output schema, the description adequately covers the tool's function. Missing details about output format or locale behavior, but overall complete for its simplicity.

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?

Only one parameter (appId) with schema description stating 'App Store Connect app ID (from list_apps)'. The description mentions this prerequisite, adding slight context beyond the schema, but schema coverage is already 100%.

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?

Clearly states the verb 'Get' and the resource 'localized metadata for an app', enumerating specific fields (title, subtitle, etc.) and providing use case (ASO review). Distinguishes from sibling 'list_apps' by requiring its output as input.

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?

Provides explicit context for use ('ASO review') and prerequisite ('Requires appId from list_apps'). However, does not explicitly state when not to use or mention alternatives among siblings.

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