Skip to main content
Glama

Create user

create_user

Create a user in an instance (like clerk users create) and return the created Backend API user object. Passwords and credential inputs are not supported; use the Clerk Dashboard or CLI for those. With dry_run, nothing is created and the request body is returned.

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": "create_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoReturn the request body without creating the user.
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
usernameNoUsername for the user. It must be unique in the instance.
last_nameNoThe user's last name.
first_nameNoThe user's first name.
external_idNoYour own system's ID for this user, stored on the Clerk user. It must be unique in the instance.
phone_numberNoPhone numbers; the first becomes primary.
email_addressNoEmail addresses; the first becomes primary.
application_idYesClerk application ID (app_…).
skip_password_requirementNoCreate the user without a password even when the instance requires one.

Output Schema

NameRequiredDescriptionDefault
idNo
bodyNo
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / body
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Raw Backend API create-user body.",
      -  "propertyNames": {
      -    "type": "string"
      -  },
      -  "type": "object"
      -}
    • addedInput schema / properties / external_id / description
      Added value: +"Your own system's ID for this user, stored on the Clerk user. It must be unique in the instance."
    • addedInput schema / properties / first_name / description
      Added value: +"The user's first name."
    • addedInput schema / properties / last_name / description
      Added value: +"The user's last name."
    • removedInput schema / properties / password
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / skip_password_requirement
      Added value: +{
      +  "description": "Create the user without a password even when the instance requires one.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / username / description
      Added value: +"Username for the user. It must be unique in the instance."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "The created Backend API user, or on a dry run { dry_run: true, body } without secrets.",
      +  "properties": {
      +    "body": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "dry_run": {
      +      "const": true,
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (which only flag non-read-only, non-idempotent, non-destructive), it discloses what is returned, that the operation has a side effect of persisting a user, and that dry_run returns the request body without creating anything. The credential limitation is an important behavioral constraint not expressible in the schema.

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 short sentences, front-loaded with the action and return value, followed by the two caveats an agent most needs. No filler or repetition of schema detail.

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 10-parameter creation tool with an output schema and full parameter descriptions, the description covers the gaps that matter: credential limitations, the CLI fallback, and dry_run behavior. Return-value explanation can be deferred to the output schema, so nothing essential is missing.

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 baseline is 3, but the description adds meaningful context: the presence of `skip_password_requirement` is contextualized by the statement that passwords cannot be supplied at all. The dry_run semantics are reinforced in prose rather than left to the schema alone.

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 and resource ("Create a user in an instance") plus the CLI equivalence (`clerk users create`) and the return value (created Backend API user object). It doesn't explicitly contrast with `update_user`, but the create-vs-update distinction is unambiguous from the verb.

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 gives a clear when-not: passwords and credential inputs aren't supported, so use the Clerk Dashboard or CLI instead. It also explains the dry_run alternative path. There's no explicit routing to siblings like `update_user`, but the exclusion and fallback guidance are concrete.

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