Skip to main content
Glama

Get Clerk user

get_user
Read-onlyIdempotent

Get a Clerk user by ID. Returns the Backend API user object without private_metadata, and a link to the user in the Clerk Dashboard. Clients that support MCP Apps also show the user as a card. To find a user ID from an email address, phone number or name, use list_users.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
userYesBackend API user object.
dashboard_urlYes
application_nameYes
environment_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read, so the description's added content is the valuable part: the response omits private_metadata, includes a Dashboard link, and renders as a card in MCP Apps clients. That redaction detail is exactly the kind of behavior an agent cannot infer from readOnlyHint. It does not describe failure behavior for a missing user ID or instance, leaving a modest gap.

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?

Three sentences, front-loaded with the action, then the return shape, then the alternative-tool routing. Nothing is repeated from the schema or annotations and no sentence is filler.

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 annotations, an output schema, and fully documented parameters, the only thing the description needs to carry is the non-obvious response behavior — which it does via the private_metadata omission and Dashboard link. Remaining gaps (error behavior on unknown user or instance) are minor for a simple read tool.

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 user_id, instance, and application_id are already documented with formats (user_…, ins_…, app_…). The description reinforces that user_id is the lookup key but adds no meaning about instance resolution or application scoping beyond the schema, so baseline 3 applies.

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?

"Get a Clerk user by ID" states a specific verb (get), resource (Clerk user), and keying mechanism (by ID). It is clearly distinguishable from list_users and from mutation siblings like update_user, so an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

It explicitly routes the agent to list_users when only an email, phone number, or name is known, which is the main lookup ambiguity for this tool. It stops short of stating prerequisites (e.g. that application_id and instance must resolve to a real instance) or what to do when no user matches, so it is clear context rather than full when/when-not guidance.

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