Skip to main content
Glama

create_person

Create a new person in Webex with details like name, email, phone, and roles. Set location, department, and manager for streamlined user management.

Instructions

Create a new person in Webex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesNoThe addresses associated with the person.
avatarNoThe avatar URL for the person.
departmentNoThe department of the person.
displayNameNoThe display name of the person.
emailsYesThe email addresses associated with the person.
extensionNoThe extension number for the person.
firstNameYesThe first name of the person.
lastNameYesThe last name of the person.
licensesNoThe licenses associated with the person.
locationIdNoThe location ID for the person.
managerNoThe name of the manager for the person.
managerIdNoThe manager ID for the person.
orgIdNoThe organization ID for the person.
phoneNumbersNoThe phone numbers associated with the person.
rolesNoThe roles assigned to the person.
siteUrlsNoThe site URLs associated with the person.
titleNoThe title of the person.

Implementation Reference

  • Handler function that executes the create_person tool by making a POST request to Webex API to create a new person.
    const executeFunction = async (personData) => {
    
      try {
        const url = getWebexUrl('/people?callingData=true&minResponse=true');
    
        const headers = {
          'Content-Type': 'application/json',
          'Authorization': `Bearer ${token}`,
          'Accept': 'application/json'
        };
    
        const response = await fetch(url, {
          method: 'POST',
          headers,
          body: JSON.stringify(personData)
        });
    
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error creating person:', error);
        return { error: 'An error occurred while creating the person.' };
      }
    };
  • Tool schema definition including name, description, and detailed input parameters schema for validation.
        type: 'function',
        function: {
          name: 'create_person',
          description: 'Create a new person in Webex.',
          parameters: {
            type: 'object',
            properties: {
              emails: {
                type: 'array',
                items: {
                  type: 'string'
                },
                description: 'The email addresses associated with the person.'
              },
              phoneNumbers: {
                type: 'array',
                items: {
                  type: 'object',
                  properties: {
                    type: { type: 'string' },
                    value: { type: 'string' }
                  }
                },
                description: 'The phone numbers associated with the person.'
              },
              extension: { type: 'string', description: 'The extension number for the person.' },
              locationId: { type: 'string', description: 'The location ID for the person.' },
              displayName: { type: 'string', description: 'The display name of the person.' },
              firstName: { type: 'string', description: 'The first name of the person.' },
              lastName: { type: 'string', description: 'The last name of the person.' },
              avatar: { type: 'string', description: 'The avatar URL for the person.' },
              orgId: { type: 'string', description: 'The organization ID for the person.' },
              roles: {
                type: 'array',
                items: { type: 'string' },
                description: 'The roles assigned to the person.'
              },
              licenses: {
                type: 'array',
                items: { type: 'string' },
                description: 'The licenses associated with the person.'
              },
              department: { type: 'string', description: 'The department of the person.' },
              manager: { type: 'string', description: 'The name of the manager for the person.' },
              managerId: { type: 'string', description: 'The manager ID for the person.' },
              title: { type: 'string', description: 'The title of the person.' },
              addresses: {
                type: 'array',
                items: {
                  type: 'object',
                  properties: {
                    type: { type: 'string' },
                    country: { type: 'string' },
                    locality: { type: 'string' },
                    region: { type: 'string' },
                    streetAddress: { type: 'string' },
                    postalCode: { type: 'string' }
                  }
                },
                description: 'The addresses associated with the person.'
              },
              siteUrls: {
                type: 'array',
                items: { type: 'string' },
                description: 'The site URLs associated with the person.'
              }
            },
            required: ['emails', 'firstName', 'lastName']
          }
        }
      }
    };
  • The apiTool object exported from the tool file, which is imported and used in tool discovery.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'create_person',
          description: 'Create a new person in Webex.',
          parameters: {
            type: 'object',
            properties: {
              emails: {
                type: 'array',
                items: {
                  type: 'string'
                },
                description: 'The email addresses associated with the person.'
              },
              phoneNumbers: {
                type: 'array',
                items: {
                  type: 'object',
                  properties: {
                    type: { type: 'string' },
                    value: { type: 'string' }
                  }
                },
                description: 'The phone numbers associated with the person.'
              },
              extension: { type: 'string', description: 'The extension number for the person.' },
              locationId: { type: 'string', description: 'The location ID for the person.' },
              displayName: { type: 'string', description: 'The display name of the person.' },
              firstName: { type: 'string', description: 'The first name of the person.' },
              lastName: { type: 'string', description: 'The last name of the person.' },
              avatar: { type: 'string', description: 'The avatar URL for the person.' },
              orgId: { type: 'string', description: 'The organization ID for the person.' },
              roles: {
                type: 'array',
                items: { type: 'string' },
                description: 'The roles assigned to the person.'
              },
              licenses: {
                type: 'array',
                items: { type: 'string' },
                description: 'The licenses associated with the person.'
              },
              department: { type: 'string', description: 'The department of the person.' },
              manager: { type: 'string', description: 'The name of the manager for the person.' },
              managerId: { type: 'string', description: 'The manager ID for the person.' },
              title: { type: 'string', description: 'The title of the person.' },
              addresses: {
                type: 'array',
                items: {
                  type: 'object',
                  properties: {
                    type: { type: 'string' },
                    country: { type: 'string' },
                    locality: { type: 'string' },
                    region: { type: 'string' },
                    streetAddress: { type: 'string' },
                    postalCode: { type: 'string' }
                  }
                },
                description: 'The addresses associated with the person.'
              },
              siteUrls: {
                type: 'array',
                items: { type: 'string' },
                description: 'The site URLs associated with the person.'
              }
            },
            required: ['emails', 'firstName', 'lastName']
          }
        }
      }
    };
    
    export { apiTool };
  • lib/tools.js:7-16 (registration)
    Central tool registration/discovery function that dynamically loads apiTool from all tool files, including create-a-person.js.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • tools/paths.js:1-54 (registration)
    List of all tool file paths used for discovery, explicitly including the create-a-person.js file.
    export const toolPaths = [
      'webex-public-workspace/webex-messaging/delete-a-message.js',
      'webex-public-workspace/webex-messaging/get-event-details.js',
      'webex-public-workspace/webex-messaging/list-teams.js',
      'webex-public-workspace/webex-messaging/delete-a-membership.js',
      'webex-public-workspace/webex-messaging/get-room-details.js',
      'webex-public-workspace/webex-messaging/delete-a-room-tab.js',
      'webex-public-workspace/webex-messaging/get-membership-details.js',
      'webex-public-workspace/webex-messaging/get-attachment-action-details.js',
      'webex-public-workspace/webex-messaging/delete-a-team-membership.js',
      'webex-public-workspace/webex-messaging/delete-a-person.js',
      'webex-public-workspace/webex-messaging/create-a-team.js',
      'webex-public-workspace/webex-messaging/delete-a-webhook.js',
      'webex-public-workspace/webex-messaging/list-room-tabs.js',
      'webex-public-workspace/webex-messaging/get-my-own-details.js',
      'webex-public-workspace/webex-messaging/get-message-details.js',
      'webex-public-workspace/webex-messaging/get-room-tab-details.js',
      'webex-public-workspace/webex-messaging/update-a-team-membership.js',
      'webex-public-workspace/webex-messaging/get-room-meeting-details.js',
      'webex-public-workspace/webex-messaging/list-ecm-folder.js',
      'webex-public-workspace/webex-messaging/update-a-team.js',
      'webex-public-workspace/webex-messaging/unlink-an-ecm-linked-folder.js',
      'webex-public-workspace/webex-messaging/list-webhooks.js',
      'webex-public-workspace/webex-messaging/delete-a-room.js',
      'webex-public-workspace/webex-messaging/delete-a-team.js',
      'webex-public-workspace/webex-messaging/get-ecm-folder-details.js',
      'webex-public-workspace/webex-messaging/get-team-membership-details.js',
      'webex-public-workspace/webex-messaging/list-direct-messages.js',
      'webex-public-workspace/webex-messaging/get-person-details.js',
      'webex-public-workspace/webex-messaging/list-team-memberships.js',
      'webex-public-workspace/webex-messaging/create-a-room-tab.js',
      'webex-public-workspace/webex-messaging/get-team-details.js',
      'webex-public-workspace/webex-messaging/edit-a-message.js',
      'webex-public-workspace/webex-messaging/get-webhook-details.js',
      'webex-public-workspace/webex-messaging/list-events.js',
      'webex-public-workspace/webex-messaging/update-a-person.js',
      'webex-public-workspace/webex-messaging/create-a-team-membership.js',
      'webex-public-workspace/webex-messaging/create-a-membership.js',
      'webex-public-workspace/webex-messaging/update-a-membership.js',
      'webex-public-workspace/webex-messaging/update-a-room-tab.js',
      'webex-public-workspace/webex-messaging/create-an-ecm-folder-configuration.js',
      'webex-public-workspace/webex-messaging/create-a-webhook.js',
      'webex-public-workspace/webex-messaging/list-memberships.js',
      'webex-public-workspace/webex-messaging/create-an-attachment-action.js',
      'webex-public-workspace/webex-messaging/update-a-room.js',
      'webex-public-workspace/webex-messaging/create-a-room.js',
      'webex-public-workspace/webex-messaging/create-a-message.js',
      'webex-public-workspace/webex-messaging/update-a-webhook.js',
      'webex-public-workspace/webex-messaging/list-rooms.js',
      'webex-public-workspace/webex-messaging/update-an-ecm-linked-folder.js',
      'webex-public-workspace/webex-messaging/list-messages.js',
      'webex-public-workspace/webex-messaging/list-people.js',
      'webex-public-workspace/webex-messaging/create-a-person.js'
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this requires admin permissions, what happens on duplicate emails, rate limits, or the response format (e.g., success confirmation or person ID). For a mutation tool with zero annotation coverage, this is inadequate.

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 with zero waste, clearly front-loading the core action. It's appropriately sized for a tool with a straightforward purpose, though brevity contributes to gaps in other dimensions.

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 tool's complexity (17 parameters, mutation operation), lack of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral aspects, usage context, or output expectations, leaving significant gaps for an AI agent to operate effectively.

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 all 17 parameters are documented in the schema. The description adds no parameter-specific information beyond implying creation, which doesn't enhance the schema's details. Baseline 3 is appropriate as the schema handles parameter documentation.

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 resource ('new person in Webex'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'create_membership' or 'create_team' beyond the resource type, missing explicit 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 alternatives like 'update_person' or 'list_people', nor does it mention prerequisites such as required permissions or organizational context. It's a basic statement without usage context.

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

Related 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/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server'

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