Skip to main content
Glama

Zoom

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Zoom List Meetings

zoom_list_meetings
Read-onlyIdempotent

List Zoom meetings for the signed-in user (upcoming, scheduled, or currently live video calls). Returns compact meeting summaries (id, topic, start time, duration, join URL, timezone). Use to browse a user's Zoom meetings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoWhich set of Zoom meetings to list: "scheduled", "live" (currently in progress), or "upcoming" (default).
page_sizeNoMaximum number of meetings to return (default 30, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "page_size": 30,
+    "type": "upcoming"
+  },
+  {
+    "type": "live"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that it returns 'compact meeting summaries' with specific fields, and clarifies the type parameter's options. No contradictions.

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

Conciseness5/5

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

Two sentences with key information front-loaded: what the tool does, what it returns, and when to use it. No superfluous content.

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

Completeness4/5

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

Given low complexity (2 optional params) and strong annotations, the description covers purpose, return fields, and usage. Could mention error cases or behavior with empty results, but not required.

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% with detailed descriptions for both parameters. The description reiterates the type enum values but adds no significant new semantics beyond the schema.

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

Purpose5/5

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

The description clearly states the verb (List), resource (Zoom meetings), and scope (signed-in user). It distinguishes from siblings like zoom_get_meeting (specific meeting) and zoom_list_recordings (recordings).

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

Usage Guidelines4/5

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

The description says to 'use to browse a user's Zoom meetings', providing clear context. It does not explicitly mention when not to use or alternatives, but sibling names implicitly guide the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zoom toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources