Skip to main content
Glama
JavaProgrammerLB

Zoom MCP Server

list_meetings

Retrieve a list of scheduled Zoom meetings filtered by type: upcoming, scheduled, or previous meetings.

Instructions

List scheduled meetings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoThe type of meeting. Choose from upcoming, scheduled or previous_meetings. upcoming - All upcoming meetings; scheduled - All valid previous (unexpired) meetings and upcoming scheduled meetings; previous_meetings - All the previous meetings;upcoming

Implementation Reference

  • Handler function that calls the Zoom API endpoint /v2/users/me/meetings with optional query params (type), then parses the response using ZoomListMeetingsSchema.
    export async function listMeetings(options: ListMeetingOptions) {
      let url = "https://api.zoom.us/v2/users/me/meetings";
      const params = new URLSearchParams();
      Object.entries(options).forEach(([key, value]) => {
        if (value !== undefined && value !== null) {
          params.append(key, value.toString());
        }
      });
      if (Array.from(params).length > 0) {
        url += `?${params.toString()}`;
      }
      const response = await zoomRequest(url, {
        method: "GET",
      });
      return ZoomListMeetingsSchema.parse(response);
    }
  • Zod schema for the input options of list_meetings tool (type parameter).
    export const ListMeetingOptionsSchema = z.object({
      type: z
        .string()
        .optional()
        .describe(
          "The type of meeting. Choose from upcoming, scheduled or previous_meetings. upcoming - All upcoming meetings; scheduled - All valid previous (unexpired) meetings and upcoming scheduled meetings; previous_meetings - All the previous meetings;",
        )
        .default("upcoming"),
    });
  • Zod schema that defines the structure of the API response for list_meetings.
    export const ZoomListMeetingsSchema = z.object({
      page_size: z.number(),
      total_records: z.number(),
      next_page_token: z.string(),
      meetings: z.array(
        z.object({
          uuid: z.string(),
          id: z.number(),
          host_id: z.string().optional(),
          topic: z.string().optional(),
          type: z.number().optional(),
          start_time: z.string().optional(),
          duration: z.number().optional(),
          timezone: z.string().optional(),
          agenda: z.string().optional(),
          created_at: z.string().optional(),
          join_url: z.string().optional(),
        }),
      ),
    });
  • index.ts:164-170 (registration)
    Tool registration in CallToolRequestSchema handler - dispatches 'list_meetings' calls to the listMeetings function.
    case "list_meetings": {
      const args = ListMeetingOptionsSchema.parse(request.params.arguments);
      const result = await listMeetings(args);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • index.ts:131-135 (registration)
    Tool registration in ListToolsRequestSchema handler - declares the list_meetings tool with its input schema.
    {
      name: "list_meetings",
      description: "List scheduled meetings",
      inputSchema: zodToJsonSchema(ListMeetingOptionsSchema),
    },
Behavior3/5

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

The description indicates a read operation (listing) with no destructive hints, but lacks explicit behavioral details such as pagination, ordering, or authentication requirements. Annotations are absent, so the description partially fulfills the transparency burden.

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

Conciseness3/5

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

The description is concise (three words) but is too brief to convey important details about the parameter and context, making it minimally adequate.

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

Completeness3/5

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

Given the single parameter with full schema coverage, no annotations, and no output schema, the description provides a basic idea but omits default behavior, return format, and any caveats. It is acceptable for a simple tool but not rich.

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 input schema has 100% description coverage for the single parameter 'type', which already explains the options. The tool description adds no additional semantic meaning beyond what the schema provides.

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 tool lists scheduled meetings, but does not differentiate from sibling tools like get_a_meeting_details or hint at the filtering parameter that modifies the set of meetings returned.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_a_meeting_details for a single meeting) or when to use different values of the 'type' parameter.

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

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