Skip to main content
Glama

update_zoom_room

Modify Zoom Room details including name, location ID, calendar resource ID, and passcode using the specified room ID. Streamlines room management via the MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendar_resource_idNoCalendar resource ID
location_idNoLocation ID
nameNoRoom name
room_idYesThe Zoom Room ID
room_passcodeNoRoom passcode

Implementation Reference

  • The handler function that executes the update_zoom_room tool logic by sending a PATCH request to the Zoom API endpoint `/rooms/{room_id}` with the provided room data, handling response and errors.
    handler: async ({ room_id, ...roomData }) => {
      try {
        const response = await zoomApi.patch(`/rooms/${room_id}`, roomData);
        return handleApiResponse(response);
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod schema defining the input parameters for the update_zoom_room tool, including required room_id and optional fields for update.
    schema: {
      room_id: z.string().describe("The Zoom Room ID"),
      name: z.string().optional().describe("Room name"),
      location_id: z.string().optional().describe("Location ID"),
      calendar_resource_id: z.string().optional().describe("Calendar resource ID"),
      room_passcode: z.string().optional().describe("Room passcode")
    },
  • src/server.js:56-56 (registration)
    Registers the zoomRoomsTools array (which contains the update_zoom_room tool definition) with the MCP server via the registerTools utility function.
    registerTools(zoomRoomsTools);
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