Skip to main content
Glama

invite-user

Create and invite new users to a Descope project by providing login credentials, contact information, roles, and invitation settings.

Instructions

Create and invite a new user to the 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
inviteUrlNoCustom URL for the invitation link
sendMailNoSend invite via email (default follows project settings)
sendSMSNoSend invite via SMS (default follows project settings)
templateIdNoCustom template ID for the invitation
templateOptionsNoOptions for customizing the invitation template

Implementation Reference

  • Handler function for 'invite-user' tool: destructures params, constructs inviteOptions merging user details and invite-specific params, calls descope.management.user.invite(loginId, inviteOptions), returns success/error markdown.
    async ({ loginId, inviteUrl, sendMail, sendSMS, templateId, templateOptions, ...userOptions }) => {
        try {
            // Define the type for invite options
            const inviteOptions: {
                inviteUrl?: string;
                sendMail?: boolean;
                sendSMS?: boolean;
                templateId?: string;
                templateOptions?: {
                    appUrl?: string;
                    redirectUrl?: string;
                    customClaims?: string;
                };
            } & typeof userOptions = {
                ...userOptions,
                inviteUrl,
                sendMail,
                sendSMS,
                templateId,
            };
    
            // Only add templateOptions if they exist and ensure customClaims is handled properly
            if (templateOptions) {
                inviteOptions.templateOptions = {
                    appUrl: templateOptions.appUrl,
                    redirectUrl: templateOptions.redirectUrl,
                };
                // Only add customClaims if it's provided
                if (templateOptions.customClaims) {
                    inviteOptions.templateOptions.customClaims = templateOptions.customClaims;
                }
            }
    
            const user = await descope.management.user.invite(loginId, inviteOptions);
    
            return {
                content: [
                    {
                        type: "text",
                        text: `Successfully invited user:\n\n${JSON.stringify(user.data, null, 2)}`,
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Error inviting user: ${error}`,
                    },
                ],
            };
        }
    },
  • Zod schema defining input parameters for invite-user tool, including user details (loginId, email, etc.), roles, tenants, and invite-specific options like inviteUrl, sendMail, template.
    {
        // Basic user info
        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"),
        // Invite specific options
        inviteUrl: z.string().url().optional()
            .describe("Custom URL for the invitation link"),
        sendMail: z.boolean().optional()
            .describe("Send invite via email (default follows project settings)"),
        sendSMS: z.boolean().optional()
            .describe("Send invite via SMS (default follows project settings)"),
        templateId: z.string().optional()
            .describe("Custom template ID for the invitation"),
        templateOptions: z.object({
            appUrl: z.string().url().optional()
                .describe("Application URL to use in the template"),
            redirectUrl: z.string().url().optional()
                .describe("URL to redirect after authentication"),
            customClaims: z.string().optional()
                .describe("Custom claims to include in the template (as JSON string)"),
        }).optional()
            .describe("Options for customizing the invitation template"),
    },
  • src/descope.ts:233-346 (registration)
    Registration of the 'invite-user' tool via server.tool(name, description, schema, handler).
    // Add invite-user tool
    server.tool(
        "invite-user",
        "Create and invite a new user to the Descope project",
        {
            // Basic user info
            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"),
            // Invite specific options
            inviteUrl: z.string().url().optional()
                .describe("Custom URL for the invitation link"),
            sendMail: z.boolean().optional()
                .describe("Send invite via email (default follows project settings)"),
            sendSMS: z.boolean().optional()
                .describe("Send invite via SMS (default follows project settings)"),
            templateId: z.string().optional()
                .describe("Custom template ID for the invitation"),
            templateOptions: z.object({
                appUrl: z.string().url().optional()
                    .describe("Application URL to use in the template"),
                redirectUrl: z.string().url().optional()
                    .describe("URL to redirect after authentication"),
                customClaims: z.string().optional()
                    .describe("Custom claims to include in the template (as JSON string)"),
            }).optional()
                .describe("Options for customizing the invitation template"),
        },
        async ({ loginId, inviteUrl, sendMail, sendSMS, templateId, templateOptions, ...userOptions }) => {
            try {
                // Define the type for invite options
                const inviteOptions: {
                    inviteUrl?: string;
                    sendMail?: boolean;
                    sendSMS?: boolean;
                    templateId?: string;
                    templateOptions?: {
                        appUrl?: string;
                        redirectUrl?: string;
                        customClaims?: string;
                    };
                } & typeof userOptions = {
                    ...userOptions,
                    inviteUrl,
                    sendMail,
                    sendSMS,
                    templateId,
                };
    
                // Only add templateOptions if they exist and ensure customClaims is handled properly
                if (templateOptions) {
                    inviteOptions.templateOptions = {
                        appUrl: templateOptions.appUrl,
                        redirectUrl: templateOptions.redirectUrl,
                    };
                    // Only add customClaims if it's provided
                    if (templateOptions.customClaims) {
                        inviteOptions.templateOptions.customClaims = templateOptions.customClaims;
                    }
                }
    
                const user = await descope.management.user.invite(loginId, inviteOptions);
    
                return {
                    content: [
                        {
                            type: "text",
                            text: `Successfully invited user:\n\n${JSON.stringify(user.data, null, 2)}`,
                        },
                    ],
                };
            } catch (error) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Error inviting 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. While it indicates this is a creation/invitation operation, it doesn't mention important behavioral aspects like required permissions, whether this sends actual invitations, what happens if the user already exists, rate limits, or what the response contains. For a mutation tool with 20 parameters, this leaves significant gaps.

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, clear sentence that efficiently communicates the core function without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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?

For a complex mutation tool with 20 parameters, no annotations, and no output schema, the description is inadequate. It doesn't address behavioral aspects, error conditions, response format, or how this differs from the 'create-user' sibling. The 100% schema coverage helps with parameters, but the overall context for using this tool remains incomplete.

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?

The schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline expectation but doesn't provide extra value. The description doesn't explain parameter relationships or usage patterns.

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 and invite') and target resource ('a new user to the Descope project'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling 'create-user' tool, which appears to be a related user creation function, so it doesn't achieve the highest score for sibling distinction.

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 the 'create-user' sibling, nor does it mention any prerequisites, constraints, or alternative scenarios. It simply states what the tool does without contextual usage information.

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'

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