Skip to main content
Glama

update_webinar

Modify webinar details such as topic, start time, duration, and settings using the Zoom API. Ensure accurate updates with structured input and proper validation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agendaNoWebinar description
durationNoWebinar duration in minutes
passwordNoPassword
settingsNoWebinar settings
start_timeNoWebinar start time
timezoneNoTime zone
topicNoWebinar topic
typeNoWebinar type
webinar_idYesThe webinar ID

Implementation Reference

  • The handler function that performs the PATCH request to update webinar details using the Zoom API.
    handler: async ({ webinar_id, ...webinarData }) => {
      try {
        const response = await zoomApi.patch(`/webinars/${webinar_id}`, webinarData);
        return handleApiResponse(response);
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod schema defining the input parameters for the update_webinar tool.
    schema: {
      webinar_id: z.string().describe("The webinar ID"),
      topic: z.string().optional().describe("Webinar topic"),
      type: z.number().min(5).max(9).optional().describe("Webinar type"),
      start_time: z.string().optional().describe("Webinar start time"),
      duration: z.number().optional().describe("Webinar duration in minutes"),
      timezone: z.string().optional().describe("Time zone"),
      password: z.string().optional().describe("Password"),
      agenda: z.string().optional().describe("Webinar description"),
      settings: z.object({}).passthrough().optional().describe("Webinar settings")
    },
  • src/server.js:48-48 (registration)
    Registers the webinarsTools array, which includes the update_webinar tool, to the MCP server.
    registerTools(webinarsTools);
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