Skip to main content
Glama
Sign In
app-publish-mcp

app-publish-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

apple_list_app_info_localizations

List localized app name, subtitle, and privacy policy URL for an App Store listing by providing an AppInfo ID. Manage international listings and compliance across languages.

Instructions

List app info localizations (app name, subtitle, privacy policy URL)

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": {
      "appInfoId": "<appInfoId>"
    },
    "name": "apple_list_app_info_localizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
appInfoIdYesAppInfo ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose safety (read-only), side effects, or any behavioral traits beyond the listing action. The agent lacks assurance about non-destructiveness.

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?

Extremely concise: one sentence with no fluff. Every word adds meaning, and the purpose is front-loaded.

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

Completeness3/5

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

The description lists key fields but omits output structure, pagination, and any prerequisites. For a simple tool with no output schema, it is minimally adequate but not comprehensive.

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 coverage is 100% and the schema description for appInfoId is minimal ('AppInfo ID'). The description adds no value beyond what the schema already provides.

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 states the action 'List app info localizations' and specifies the resource (localizations) and included fields (app name, subtitle, privacy policy URL), making the tool's purpose distinct from siblings like apple_get_app_info.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives, nor any prerequisites like needing an appInfoId. Usage is implied but not clarified with exclusions or context.

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