Skip to main content
Glama

List native applications

list_native_applications
Read-onlyIdempotent

List the iOS and Android apps registered with an instance and whether its Native API is enabled, as the Clerk Dashboard's Native applications page shows them. Returns native_api_enabled, ios (each with id, bundle_id, and app_id_prefix), and android (each with id, package_name, namespace, and fingerprints).

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>"
    },
    "name": "list_native_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
iosYes
androidYes
native_api_enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the returned field set (native_api_enabled, ios/android structures), but that largely duplicates the existing output schema, and it says nothing about pagination, result ordering, or behavior when an instance has no native apps.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and resource, then the return shape. No filler, no restatement of the title, and the Dashboard analogy is compact and informative.

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?

With rich annotations, a fully described two-parameter schema, and an output schema, the definition is essentially complete for correct invocation. The only shortfall is the absence of sibling differentiation, which matters given the nearby list_applications and enable_native_api tools.

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%, with both parameters (instance, application_id) documented including formats and the development/production values. The description contributes no additional parameter meaning, which is the expected baseline when the schema carries the full burden.

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?

States a specific verb ('List') and a precise resource ('iOS and Android apps registered with an instance'), plus the key attribute (whether Native API is enabled). This is clearly distinct from generic app listing, but it never names or contrasts with the sibling list_applications tool, so an agent must infer the boundary between them.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'registered with an instance' and the reference to the Dashboard's Native applications page. There is no explicit when-to-use guidance, no mention of when to prefer list_applications, and no note that enable_native_api is the mutation counterpart.

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