Skip to main content
Glama
JavaProgrammerLB

Zoom MCP Server

create_meeting

Schedule a Zoom meeting by specifying topic, agenda, start time, and timezone. Use this to set up online meetings with custom details.

Instructions

Create a meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agendaNoThe meeting's agenda.New Meeting's agenda
start_timeNoThe meeting's start time. This supports local time and GMT formats.To set a meeting's start time in GMT, use the yyyy-MM-ddTHH:mm:ssZ date-time format. For example, 2020-03-31T12:02:00Z. To set a meeting's start time using a specific timezone, use the yyyy-MM-ddTHH:mm:ss date-time format and specify the timezone ID in the timezone field. If you do not specify a timezone, the timezone value defaults to your Zoom account's timezone. You can also use UTC for the timezone value. Note: If no start_time is set for a scheduled meeting, the start_time is set at the current time and the meeting type changes to an instant meeting, which expires after 30 days. current time is 2026-05-04T21:45:46.369Z.
timezoneNoTimezone for the meeting's start time. The Current timezone is UTC.
topicNoThe meeting's topic.

Implementation Reference

  • The 'createMeeting' async function that sends a POST request to Zoom API to create a meeting. It takes CreateMeetingOptions, calls zoomRequest, and parses the response with ZoomMeetingSchema.
    export async function createMeeting(options: CreateMeetingOptions) {
      const response = await zoomRequest(
        `https://api.zoom.us/v2/users/me/meetings`,
        {
          method: "POST",
          body: options,
        },
      );
      return ZoomMeetingSchema.parse(response);
    }
  • CreateMeetingOptionsSchema - Zod schema defining input validation for create_meeting tool with fields: agenda, start_time, timezone, and topic.
    export const CreateMeetingOptionsSchema = z.object({
      agenda: z
        .string()
        .max(2000)
        .describe("The meeting's agenda.")
        .default("New Meeting's agenda"),
      start_time: z
        .string()
        .optional()
        .describe(
          `The meeting's start time. This supports local time and GMT formats.To set a meeting's start time in GMT, use the yyyy-MM-ddTHH:mm:ssZ date-time format. For example, 2020-03-31T12:02:00Z. To set a meeting's start time using a specific timezone, use the yyyy-MM-ddTHH:mm:ss date-time format and specify the timezone ID in the timezone field. If you do not specify a timezone, the timezone value defaults to your Zoom account's timezone. You can also use UTC for the timezone value. Note: If no start_time is set for a scheduled meeting, the start_time is set at the current time and the meeting type changes to an instant meeting, which expires after 30 days. current time is ${new Date().toISOString()}.`,
        ),
      timezone: z
        .string()
        .optional()
        .describe(
          `Timezone for the meeting's start time. The Current timezone is ${Intl.DateTimeFormat().resolvedOptions().timeZone}.`,
        ),
      topic: z.string().max(200).optional().describe("The meeting's topic."),
    });
  • TypeScript type CreateMeetingOptions inferred from the Zod schema.
    export type CreateMeetingOptions = z.infer<typeof CreateMeetingOptionsSchema>;
  • index.ts:123-148 (registration)
    Registration of 'create_meeting' tool in ListToolsRequestSchema handler, defining its name, description, and inputSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "create_meeting",
            description: "Create a meeting",
            inputSchema: zodToJsonSchema(CreateMeetingOptionsSchema),
          },
          {
            name: "list_meetings",
            description: "List scheduled meetings",
            inputSchema: zodToJsonSchema(ListMeetingOptionsSchema),
          },
          {
            name: "delete_a_meeting",
            description: "Delete a meeting with a given ID",
            inputSchema: zodToJsonSchema(DeleteMeetingOptionsSchema),
          },
          {
            name: "get_a_meeting_details",
            description: "Retrieve the meeting's details with a given ID",
            inputSchema: zodToJsonSchema(GetMeetingOptionsSchema),
          },
        ],
      };
    });
  • CallToolRequestSchema handler that dispatches 'create_meeting' - parses arguments with CreateMeetingOptionsSchema and calls createMeeting().
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      try {
        if (!request.params.arguments) {
          throw new Error("No arguments provided");
        }
        switch (request.params.name) {
          case "create_meeting": {
            const args = CreateMeetingOptionsSchema.parse(request.params.arguments);
            const result = await createMeeting(args);
            return {
              content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
            };
          }
Behavior1/5

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

No annotations are provided, and the description provides no behavioral traits beyond the trivial 'Create a meeting'. Important details like authentication, side effects, or response are missing.

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

Conciseness2/5

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

The description is a single sentence that merely repeats the tool name, failing to earn its place by providing any useful information beyond the identifier.

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?

With 4 parameters, no annotations, and no output schema, the description is severely inadequate; it does not explain return values, prerequisites, or expected behavior.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters.

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

Purpose2/5

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

The description is a tautology, restating the tool name without adding specificity or distinguishing from siblings like delete_a_meeting.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance, but the sibling tools are clearly different operations (delete, get, list), so usage is implied.

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