Skip to main content
Glama

create_sub_account

Create sub-accounts for Zoom users by providing essential details such as name, email, password, company, and country. Streamlines account management within the Zoom API MCP Server environment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNoAddress
cityNoCity
company_nameYesCompany name
countryYesCountry
emailYesEmail address of the account owner
first_nameYesFirst name of the account owner
last_nameYesLast name of the account owner
passwordYesPassword
phone_countryNoCountry for phone
phone_numberNoPhone number
stateNoState/Province
zipNoZIP/Postal Code

Implementation Reference

  • Handler function that creates a sub account by posting the account data to the Zoom API /accounts endpoint.
    handler: async (accountData) => {
      try {
        const response = await zoomApi.post('/accounts', accountData);
        return handleApiResponse(response);
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod schema defining the input parameters for creating a sub account.
    schema: {
      first_name: z.string().describe("First name of the account owner"),
      last_name: z.string().describe("Last name of the account owner"),
      email: z.string().email().describe("Email address of the account owner"),
      password: z.string().describe("Password"),
      phone_country: z.string().optional().describe("Country for phone"),
      phone_number: z.string().optional().describe("Phone number"),
      company_name: z.string().describe("Company name"),
      address: z.string().optional().describe("Address"),
      city: z.string().optional().describe("City"),
      state: z.string().optional().describe("State/Province"),
      zip: z.string().optional().describe("ZIP/Postal Code"),
      country: z.string().describe("Country")
    },
  • src/server.js:49-49 (registration)
    Registers the accountTools array (containing create_sub_account tool) with the MCP server.
    registerTools(accountTools);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/mattcoatsworth/zoom-mcp-server'

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