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

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Read] Get age rating declaration

asc_age_rating_get

Retrieve an app's current App Store age rating questionnaire answers, including content descriptors, Kids Age Band, and overrides. Check or audit age rating settings before submission.

Instructions

Read-only. Gets the current App Store age rating questionnaire answers for an app (content descriptors, Kids Age Band, age rating overrides).

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

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explicitly states 'Read-only' and clarifies it retrieves current answers, providing key behavioral context. It does not disclose potential error states or response format, but given the simplicity of the operation, this is adequate.

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 a single efficient sentence preceded by 'Read-only.' It immediately communicates the most important behavior and lists the specific data returned without unnecessary detail. Every word serves a purpose.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description sufficiently explains what is retrieved. It mentions the specific components of the questionnaire, making the tool's purpose clear for an agent. It could benefit from noting that the answer would be for a single app, but the parameter name implies that.

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?

The schema has 100% coverage with a clear description for appId ('Bundle id, app name, or App Store Connect app id'). The tool description adds no additional parameter semantics, so the baseline of 3 applies.

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 tool gets the current App Store age rating questionnaire answers for an app, specifying content descriptors, Kids Age Band, and overrides. It uses the verb 'Gets' and identifies the resource, distinguishing it from the update sibling tool by declaring it 'Read-only'.

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?

Usage context is implied: this tool is for retrieving current age rating answers, while the update sibling would be for modifications. However, the description does not explicitly state when to use this tool versus alternatives or mention any exclusions, so it relies on implication.

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