Skip to main content
Glama
SShadowS

Zendesk MCP Server

by SShadowS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_user

Create a new Zendesk user by providing name and unique email. Assign roles (end-user, agent, admin), add tags, notes, phone, or organization ID. Returns the full profile and auto-assigned ID.

Instructions

Create a new Zendesk user. Email must be unique across the instance — duplicates return 422. Role defaults to end-user; specify agent or admin for staff accounts. Returns the created user's full profile including the auto-assigned ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUser's full name
roleNoUser's role
tagsNoTags for the user
emailYesUser's email address
notesNoNotes about the user
phoneNoUser's phone number
organization_idNoID of the user's organization

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses key side effects: duplicate email returns 422, role defaults to end-user, and the response includes the full profile with the auto-assigned ID. It stops short of covering auth requirements or other error cases, but for a creation tool this is substantive disclosure.

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 with no filler. The core action is front-loaded, and each sentence adds a distinct piece of behavioral information: uniqueness, role default, and return shape.

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?

For a 7-parameter creation tool with no output schema, the description covers the most decision-relevant aspects: required uniqueness, role behavior, and response contents. It does not discuss optional field semantics or authentication, but these are either self-evident or less critical for an agent deciding whether to invoke.

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?

The schema already documents all 7 parameters at 100% coverage, so baseline is 3. The description adds value beyond the schema by clarifying the role default and the uniqueness constraint on email, both of which affect invocation correctness.

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?

The description opens with 'Create a new Zendesk user', naming a specific verb and resource. The intent is unambiguous and naturally distinguishes this from sibling tools like update_user, delete_user, and get_user.

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?

The description provides clear operational context: email uniqueness, role default, and what the call returns. It implies use when creating a new user, but does not explicitly name alternatives or exclusion scenarios. This is clear context without formal when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools