Skip to main content
Glama

list_phone_users

Retrieve a list of Zoom phone users by specifying site ID, page size, and next page token for efficient user management and integration with Zoom API MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
next_page_tokenNoNext page token
page_sizeNoNumber of records returned
site_idNoSite ID

Implementation Reference

  • The handler function constructs query parameters from inputs and calls the Zoom API GET /phone/users endpoint to list phone users, then processes the response or error.
    handler: async ({ page_size, next_page_token, site_id }) => {
      try {
        const params = {};
        if (page_size) params.page_size = page_size;
        if (next_page_token) params.next_page_token = next_page_token;
        if (site_id) params.site_id = site_id;
        
        const response = await zoomApi.get('/phone/users', { params });
        return handleApiResponse(response);
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod-based input schema defining optional parameters for pagination (page_size, next_page_token) and filtering (site_id).
    schema: {
      page_size: z.number().min(1).max(300).optional().describe("Number of records returned"),
      next_page_token: z.string().optional().describe("Next page token"),
      site_id: z.string().optional().describe("Site ID")
    },
  • src/server.js:51-51 (registration)
    Registers the entire phoneTools array (imported from './tools/phone.js'), which includes the 'list_phone_users' tool, with the MCP server using the generic registerTools function.
    registerTools(phoneTools);
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