Skip to main content
Glama
Sign In
pofky

asc-mcp

by pofky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set the age rating

set_age_rating
Destructive

Set an App Store Connect app's age-rating content declarations so Apple calculates the 4+/9+/12+/17+ rating based on your responses.

Instructions

Set the app's age-rating content declarations (Apple computes 4+/9+/12+/17+). Pass a declarations map, e.g. { medicalOrTreatmentInformation: "INFREQUENT_OR_MILD" }. Pro feature.

Input Schema

NameRequiredDescriptionDefault
app_idYesApp Store Connect app ID
declarationsYesMap of declaration key to value. Frequency keys take NONE/INFREQUENT_OR_MILD/FREQUENT_OR_INTENSE (also INFREQUENT/FREQUENT for the few keys Apple uses those on); capability keys take true/false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.14
    • removedInput schema / properties / declarations / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / declarations / additionalProperties / type
      Added value: +[
+  "string",
+  "boolean"
+]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/destructive profile is covered structurally. The description usefully adds that Apple computes the final tier from the declarations (so the caller passes inputs, not a rating), but it does not clarify whether the declarations map replaces or merges with existing declarations.

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?

Three short sentences with zero filler: purpose, then the call pattern with an example, then the Pro gating. The most important information is front-loaded.

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

Completeness5/5

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

For a two-parameter mutation tool with full schema coverage and annotations carrying the safety profile, the description covers purpose, the nested-map shape, and the gating constraint. No output schema exists, so nothing about return values is owed here.

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?

Schema description coverage is 100%, so the baseline is 3; the description earns an extra point by giving a concrete example key ('medicalOrTreatmentInformation') that the schema only describes generically, making the map's shape immediately usable.

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

Purpose4/5

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

States a specific verb and resource ('Set the app's age-rating content declarations') and clarifies the outcome (Apple computes 4+/9+/12+/17+), which separates it from adjacent mutation tools like set_app_metadata. It does not explicitly name any sibling, so it stops short of a 5.

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 is only implied — an agent infers this is the tool for age-rating declarations. The 'Pro feature' note is a useful gating prerequisite, but there is no when-to-use/when-not guidance and no alternative named for related metadata tasks.

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