Skip to main content
Glama

Draft a featuring nomination

app_nomination_create

A featuring nomination as a draft in App Store Connect: asks Apple's editors to consider the app for featuring around a date, for a launch, an update or new content. Apple asks for at least two weeks' notice and up to three months for wider consideration. The description is written to an editor: what is new, for whom, why it matters to them, and who made it and why, plainly, with no superlatives. Link the in-app event it is about. The founder submits it (App Store Connect, Featuring, Nominations). Growth. Free.

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": {
      "name": "<name>",
      "type": "<type>",
      "description": "<description>",
      "publishStartDate": "<publishStartDate>"
    },
    "name": "app_nomination_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesInternal name
typeYes
appIdNo
notesNo
localesNo
descriptionYesWhat is new, for whom, why it matters, and the story behind it
territoriesNoApple's three-letter territory codes; left out, every territory
inAppEventIdsNoThe in-app events it is about (app_featuring, app_events)
deviceFamiliesNoThe devices the app runs well on
hasInAppEventsNo
publishEndDateNo
preOrderEnabledNo
publishStartDateYesISO date to be featured from: the release date or the moment's first day
supplementalMaterialsUrisNoA press kit, a video, the app's site
launchInSelectMarketsFirstNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"What is new, for whom, and why it matters"New value: +"What is new, for whom, why it matters, and the story behind it"
    • addedInput schema / properties / deviceFamilies
      Added value: +{
      +  "description": "The devices the app runs well on",
      +  "items": {
      +    "enum": [
      +      "IPHONE",
      +      "IPAD",
      +      "APPLE_TV",
      +      "APPLE_WATCH",
      +      "MAC",
      +      "VISION"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 6,
      +  "type": "array"
      +}
    • addedInput schema / properties / inAppEventIds
      Added value: +{
      +  "description": "The in-app events it is about (app_featuring, app_events)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • addedInput schema / properties / launchInSelectMarketsFirst
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / preOrderEnabled
      Added value: +{
      +  "type": "boolean"
      +}
    • changedInput schema / properties / publishStartDate / description
      Previous value: -"ISO date to be featured from: the release date"New value: +"ISO date to be featured from: the release date or the moment's first day"
    • addedInput schema / properties / territories
      Added value: +{
      +  "description": "Apple's three-letter territory codes; left out, every territory",
      +  "items": {
      +    "maxLength": 3,
      +    "minLength": 3,
      +    "type": "string"
      +  },
      +  "maxItems": 200,
      +  "type": "array"
      +}
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, and the description is consistent with a non-destructive draft creation. It adds real context beyond the annotations — the notice window and the fact that Apple's editors are the audience — but says nothing about what the draft state means afterward, whether it can be edited or must be submitted separately, or what the response contains.

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

Conciseness3/5

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

The purpose is front-loaded and the editorial advice earns its place, but the text wanders into style coaching and ends with two bare taxonomy fragments ('Growth. Free.') and a UI navigation path that add little for an agent. Trimming the trailing tags would tighten it without losing meaning.

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?

For a 15-parameter, no-output-schema mutation tool, the description conveys the intent and the key editorial requirement but leaves the majority of parameters unexplained and gives no sense of the returned object. It is adequate to understand the tool, not fully sufficient to invoke it confidently without reading the schema.

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 only 47% across 15 parameters, so the description has to compensate and only partly does. It elaborates the 'description' payload (what is new, for whom, why it matters, who made it, no superlatives) and ties publishStartDate to the release/moment date and inAppEventIds to the linked event, but appId, type, notes, locales, hasInAppEvents, publishEndDate, preOrderEnabled and launchInSelectMarketsFirst get no explanation anywhere.

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?

The description names a specific verb and resource — drafting a featuring nomination in App Store Connect — and clarifies that it asks Apple's editors to consider the app around a date. It is distinguishable from the sibling app_featuring (which reads featuring state) though it never names that sibling explicitly to make the contrast airtight.

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?

It gives concrete triggering contexts (a launch, an update, or new content) and timing constraints: at least two weeks' notice, up to three months for wider consideration. What is missing is any explicit when-not guidance or pointer to sibling tools such as app_featuring or app_event_create for related work.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources