Skip to main content
Glama

Register an iOS application

create_ios_application

Register an iOS app's bundle ID and App ID Prefix with an instance, like adding an iOS app on the Clerk Dashboard's Native applications page. Returns the registered app, with its id, bundle_id, and app_id_prefix. Clerk needs the registration for native sign-in with Clerk's iOS SDK, and before patch_instance_config can set the app's minimum version (native_app_minimum_versions). Check list_native_applications first. The same bundle ID can be registered again under a different App ID Prefix, for example after the app moves to another Apple developer team, so confirm the prefix before adding a second one. Registering the same bundle ID and prefix again is rejected, and so is a bundle ID that differs from a registered one only in capitalization. To change or remove a registration, use the Clerk Dashboard. Then run enable_native_api if it isn't enabled.

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": {
      "application_id": "<application_id>",
      "instance": "<instance>",
      "bundle_id": "<bundle_id>",
      "app_id_prefix": "<app_id_prefix>"
    },
    "name": "create_ios_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
bundle_idYesThe app's bundle ID, exactly as Xcode spells it, such as com.example.app.
app_id_prefixYesThe app's ten-character Apple App ID Prefix, such as ABCDE12345. For most apps it's the Apple Developer Team ID; confirm it on the app's identifier in the Apple Developer portal.
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
idYes
bundle_idYes
app_id_prefixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare mutation (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds substantial context beyond that: duplicate rejection rules, the capitalization collision rule, the allowance for re-registering a bundle ID under a different prefix, and that updates/deletes are not possible via the API. It does not discuss rate limits or any auth scope, which keeps it short of a 5.

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?

Front-loads the action and return value, then moves to ordering, duplicate rules and follow-ups, with every sentence carrying distinct information. It is dense and slightly long for a single tool, but there is little filler to remove.

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

Completeness4/5

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

Complete for a mutating registration tool: prerequisites, duplicate-failure modes, follow-up calls and the fact that remediation requires the Dashboard are all stated, and an output schema covers return values. Only minor gaps remain around permissions and behavior on partial conflicts.

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?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining why app_id_prefix matters (it identifies the Apple developer team and can legitimately change), which is semantics not present in the schema's pattern description. It does not individually explain instance or application_id, but those are already well documented.

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?

States a specific verb and resource: register an iOS app's bundle ID and App ID Prefix with an instance, and ties it to the Dashboard's Native applications page. It also implicitly distinguishes itself from create_android_application and list_native_applications by naming the iOS-specific registration artifact.

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

Usage Guidelines5/5

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

Gives explicit ordering: check list_native_applications first, run enable_native_api if not enabled, and use the Dashboard (not this tool) to change or remove a registration. It also explains the prerequisite relationship to patch_instance_config's native_app_minimum_versions.

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