Skip to main content
Glama
descope-sample-apps

descope-mcp-server

Official

create-user

Create new users in Descope projects by defining login IDs, email, phone, roles, and tenant associations for identity management.

Instructions

Create a new user in Descope project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginIdYesPrimary login identifier for the user
additionalLoginIdsNoAdditional login identifiers
emailNoUser's email address
verifiedEmailNoWhether the email is pre-verified
phoneNoUser's phone number in E.164 format
verifiedPhoneNoWhether the phone is pre-verified
displayNameNoUser's display name
givenNameNoUser's given/first name
middleNameNoUser's middle name
familyNameNoUser's family/last name
pictureNoURL to user's profile picture
rolesNoGlobal role names to assign to the user
userTenantsNoTenant associations with specific roles
ssoAppIdsNoSSO application IDs to associate
customAttributesNoCustom attributes for the user

Implementation Reference

  • The async handler function for the 'create-user' tool. It destructures input params, calls descope.management.user.create, and returns a text content response with the user data or error.
    async ({ loginId, ...options }) => {
        try {
            const user = await descope.management.user.create(loginId, options);
    
            return {
                content: [
                    {
                        type: "text",
                        text: `Successfully created user:\n\n${JSON.stringify(user.data, null, 2)}`,
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Error creating user: ${error}`,
                    },
                ],
            };
        }
    },
  • Zod input schema for the 'create-user' tool parameters, validating fields like loginId, email, phone, names, roles, tenants, etc.
    {
        loginId: z.string()
            .describe("Primary login identifier for the user"),
        additionalLoginIds: z.array(z.string()).optional()
            .describe("Additional login identifiers"),
        email: z.string().email().optional()
            .describe("User's email address"),
        verifiedEmail: z.boolean().optional()
            .describe("Whether the email is pre-verified"),
        phone: z.string().optional()
            .describe("User's phone number in E.164 format"),
        verifiedPhone: z.boolean().optional()
            .describe("Whether the phone is pre-verified"),
        displayName: z.string().optional()
            .describe("User's display name"),
        givenName: z.string().optional()
            .describe("User's given/first name"),
        middleName: z.string().optional()
            .describe("User's middle name"),
        familyName: z.string().optional()
            .describe("User's family/last name"),
        picture: z.string().url().optional()
            .describe("URL to user's profile picture"),
        roles: z.array(z.string()).optional()
            .describe("Global role names to assign to the user"),
        userTenants: z.array(z.object({
            tenantId: z.string(),
            roleNames: z.array(z.string()),
        })).optional()
            .describe("Tenant associations with specific roles"),
        ssoAppIds: z.array(z.string()).optional()
            .describe("SSO application IDs to associate"),
        customAttributes: z.record(z.any()).optional()
            .describe("Custom attributes for the user"),
    },
  • src/descope.ts:170-231 (registration)
    Registration of the 'create-user' tool on the MCP server using server.tool(name, description, inputSchema, handlerFn). This is within the createServer function.
    server.tool(
        "create-user",
        "Create a new user in Descope project",
        {
            loginId: z.string()
                .describe("Primary login identifier for the user"),
            additionalLoginIds: z.array(z.string()).optional()
                .describe("Additional login identifiers"),
            email: z.string().email().optional()
                .describe("User's email address"),
            verifiedEmail: z.boolean().optional()
                .describe("Whether the email is pre-verified"),
            phone: z.string().optional()
                .describe("User's phone number in E.164 format"),
            verifiedPhone: z.boolean().optional()
                .describe("Whether the phone is pre-verified"),
            displayName: z.string().optional()
                .describe("User's display name"),
            givenName: z.string().optional()
                .describe("User's given/first name"),
            middleName: z.string().optional()
                .describe("User's middle name"),
            familyName: z.string().optional()
                .describe("User's family/last name"),
            picture: z.string().url().optional()
                .describe("URL to user's profile picture"),
            roles: z.array(z.string()).optional()
                .describe("Global role names to assign to the user"),
            userTenants: z.array(z.object({
                tenantId: z.string(),
                roleNames: z.array(z.string()),
            })).optional()
                .describe("Tenant associations with specific roles"),
            ssoAppIds: z.array(z.string()).optional()
                .describe("SSO application IDs to associate"),
            customAttributes: z.record(z.any()).optional()
                .describe("Custom attributes for the user"),
        },
        async ({ loginId, ...options }) => {
            try {
                const user = await descope.management.user.create(loginId, options);
    
                return {
                    content: [
                        {
                            type: "text",
                            text: `Successfully created user:\n\n${JSON.stringify(user.data, null, 2)}`,
                        },
                    ],
                };
            } catch (error) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Error creating user: ${error}`,
                        },
                    ],
                };
            }
        },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a user but doesn't mention required permissions, whether the operation is idempotent, what happens on duplicate loginIds, or what the response contains. For a mutation tool with 15 parameters, this leaves critical behavioral traits undocumented.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero wasted verbiage. Every word earns its place.

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

Completeness2/5

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

Given the complexity (15 parameters, nested objects, no output schema, and no annotations), the description is inadequate. It doesn't explain what happens after creation, error conditions, or system behavior. For a user creation tool in an authentication system, this leaves too many contextual gaps for reliable agent operation.

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 all 15 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema. This meets the baseline of 3 when the schema does the heavy lifting, but the description doesn't compensate with any extra context about parameter interactions or requirements.

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?

The description clearly states the action ('Create a new user') and the resource ('in Descope project'), providing a specific verb+resource combination. However, it doesn't differentiate from the sibling 'invite-user' tool, which likely serves a related purpose. The purpose is clear but lacks sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'invite-user'. There's no mention of prerequisites, context, or exclusions. The agent must infer usage from the tool name alone, which is insufficient for informed selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/descope-sample-apps/descope-mcp-server-stdio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server