app-publish-mcp

apple_create_profile

Create a provisioning profile for iOS app development or distribution. Specify profile type, bundle ID, certificates, and device IDs for development profiles.

Instructions

Create a provisioning profile

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>",
      "profileType": "<profileType>",
      "bundleIdId": "<bundleIdId>",
      "certificateIds": "<certificateIds>"
    },
    "name": "apple_create_profile"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Profile name
`deviceIds`	No	Array of device IDs (required for development profiles)
`bundleIdId`	Yes	Bundle ID
`profileType`	Yes	Profile type (e.g. IOS_APP_DEVELOPMENT, IOS_APP_STORE)
`certificateIds`	Yes	Array of certificate IDs

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 full responsibility for disclosing behavioral traits. It only states the action without mentioning side effects, authorization needs, or any constraints beyond the schema. Mutations like profile creation typically involve dependencies and potential errors, which are not addressed.

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 very short and concise, consisting of a single sentence. It is front-loaded with the action. However, given the complexity and importance of profile creation, a slightly more detailed description would be justified without becoming verbose.

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 there is no output schema, the description should explain what is returned upon creation (e.g., profile ID, profile object). It also does not clarify conditional requirements (e.g., deviceIds needed for development profiles) or the relationship with other resources. The description is incomplete for a user to fully understand the tool's behavior.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds no additional meaning to the parameters beyond what the schema already provides. The schema itself has clear descriptions for each parameter.

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 clearly states the action and resource ('Create a provisioning profile'). It effectively distinguishes from siblings like 'apple_delete_profile' and 'apple_list_profiles'. However, it could be more specific about the scope (e.g., iOS, macOS) but the 'profileType' parameter covers this.

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?

No guidance is provided on when to use this tool vs alternatives. There is no mention of prerequisites (e.g., needing certificates, bundle IDs, or devices) or conditions under which the tool should or 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