Skip to main content
Glama

Register an Android application

create_android_application

Register an Android app's package name with an instance, like adding an Android app on the Clerk Dashboard's Native applications page. Returns the registered app, with its id, package_name, namespace, and fingerprints. Clerk needs the registration for native sign-in with Clerk's Android SDK, and before patch_instance_config can set the app's minimum version (native_app_minimum_versions). Check list_native_applications first: a package name that's already registered is rejected. 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>",
      "package_name": "<package_name>"
    },
    "name": "create_android_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
namespaceNoThe Digital Asset Links namespace. Omit it to use android_app, which almost every app uses.
fingerprintsNoSHA-256 fingerprints of the app's signing certificates, such as 14:6D:E9:…. Passkeys need them; omit them otherwise.
package_nameYesThe app's package name (its applicationId), such as com.example.app.
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
idYes
namespaceYes
fingerprintsYes
package_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic profile (not read-only, not idempotent, not destructive); the description adds the operationally important detail that a duplicate package name 'is rejected', that mutations/removals must happen outside this tool, and that registration is a prerequisite for other operations. It also names the returned fields, which goes beyond what the annotations convey.

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?

Sentences are dense but each carries information: analog, return shape, prerequisites, dedupe guard, exclusion, follow-up step. Slight structural weakness in that the list_native_applications check appears after the patch_instance_config dependency rather than front-loaded with the other preconditions.

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

Completeness5/5

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

For a mutation tool with an output schema already defined, the description covers everything an agent needs: what it registers, duplicate handling, ordering with enable_native_api and patch_instance_config, and where update/delete must go instead.

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 description coverage is 100%, so the schema already documents instance, namespace defaults, fingerprint format, package_name pattern, and application_id. The description mentions namespace and fingerprints only as returned fields rather than adding usage meaning (e.g. when to supply fingerprints), so it does not meaningfully exceed the baseline.

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 concrete verb and resource ('Register an Android app's package name with an instance') and anchors it to a familiar analog ('like adding an Android app on the Clerk Dashboard's Native applications page'). It also implicitly separates itself from create_ios_application by scoping to Android package names.

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 prerequisites ('Check list_native_applications first'), downstream sequencing ('before patch_instance_config can set the app's minimum version', 'Then run enable_native_api if it isn't enabled'), and an explicit exclusion ('To change or remove a registration, use the Clerk Dashboard'). Both when-to-use and when-not-to-use are covered.

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