app-publish-mcp

apple_create_bundle_id

Create a new Apple bundle ID on App Store Connect by specifying the identifier, display name, and platform (iOS, macOS, or universal).

Instructions

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

Input Schema

Name	Required	Description
`name`	Yes	Display name
`platform`	Yes
`identifier`	Yes	Bundle ID (e.g. com.example.app)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the obvious action without mentioning idempotency, duplicate handling, required permissions, or side effects. The lack of depth fails to inform the agent of important behaviors.

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

Conciseness4/5

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

The description is a single, concise sentence at the front. It is efficiently short, though it sacrifices necessary detail. It meets the standard for brevity but lacks substantive content to earn a 5.

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

Completeness2/5

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

Given the tool has three required parameters, no output schema, and no annotations, the description is insufficient. It does not explain uniqueness constraints, failure behaviors, or return values. The minimal text leaves the agent underinformed for a registration operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes two of three parameters (identifier and name), and the description adds no additional meaning. The 'platform' parameter has an enum but no explanation of its implications. The description does not compensate for the schema's limited coverage.

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 'Register a new bundle ID' uses a specific verb and resource, clearly distinguishing this tool from siblings like 'apple_list_bundle_ids' (list) or 'apple_create_certificate' (different resource). The action is unambiguous and directly maps to its purpose.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool over alternatives, nor does it mention prerequisites, constraints, or cases where the tool should not be used. The agent receives no contextual information to decide between this and similar creation tools.

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

Deploy Server