Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_bundle_id

Register a new bundle ID in App Store Connect by providing its identifier, name, and platform to prepare an app for development and distribution.

Instructions

Register a new bundle ID for app development

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

NameRequiredDescriptionDefault
nameYesA name for the bundle ID
seedIdNoYour team's seed ID (optional)
platformYesThe platform for this bundle ID
identifierYesThe bundle ID string (e.g., 'com.example.app')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must cover behavioral traits. It only says 'Register' (indicating creation) but does not disclose idempotency, permissions, side effects, or return behavior. Missing critical context for a mutation operation.

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 description is a single, short sentence, but it is not front-loaded with the most critical information (e.g., the action and resource). It is adequate but unremarkable.

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?

Despite 4 parameters and no output schema, the description lacks details about post-creation behavior (e.g., what is returned, if the ID is immediately usable). The tool is incompletely specified for an agent to understand the full effect.

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 100%, so the input schema already documents all parameters. The description adds no additional parameter-level meaning. Baseline score of 3 is appropriate.

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?

Clear verb ('Register') and specific resource ('bundle ID') stated. Distinct from sibling tools like list_bundle_ids and get_bundle_id_info.

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 only a vague context ('for app development') but no explicit guidance on when to use this tool versus alternatives (e.g., when to create vs. list or get).

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