App Store Connect MCP Server

create_bundle_id

Instructions

Register a new bundle ID in App Store Connect. The identifier must be unique and follow reverse-domain notation (e.g., com.example.app).

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": {
      "identifier": "<identifier>",
      "name": "<name>",
      "platform": "<platform>"
    },
    "name": "create_bundle_id"
  }
}

Input Schema

Name	Required	Description
`identifier`	Yes	The bundle identifier (e.g., com.example.app)
`name`	Yes	A name for the bundle ID
`platform`	Yes	The platform for this bundle ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0May 29, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description alone must disclose behavioral traits. It states the action is to 'register' (a creation), but does not reveal side effects (e.g., whether registration affects existing resources, reversibility, or quotas). This is insufficient for a mutation tool.

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 two concise sentences with no wasted words. The first sentence front-loads the purpose, and the second provides a key parameter detail. It is appropriately sized for the tool's simplicity.

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?

Given no annotations and no output schema, the description provides basic information but lacks completeness for a creation tool. It does not explain return values, error conditions, or constraints like maximum number of bundle IDs, which the agent may need to know for correct invocation.

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?

The schema covers all three parameters with descriptions. The description adds meaningful context for the 'identifier' parameter by specifying reverse-domain notation and uniqueness, which goes beyond the schema. It does not add detail for 'name' or 'platform', but the schema is clear.

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 verb 'Register' and the resource 'bundle ID' with the system 'App Store Connect'. It distinguishes from sibling tools like 'list_bundle_ids', 'update_bundle_id', and 'delete_bundle_id' by indicating a creation action.

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?

The description provides a key usage condition: the identifier must be unique and follow reverse-domain notation. However, it does not explicitly mention when to use this tool versus alternative creation tools like 'create_app_version' or 'add_beta_tester', nor does it exclude scenarios where it should not be used.

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

Deploy Server