Skip to main content
Glama

meetings_create

Create an online video meeting on the workspace's own Zoom account and get its join link. Needs the workspace's Zoom connected (channels.connect with channel='zoom' gives the sign-in link); without it the tool refuses. Anyone with the link enters directly (no waiting room). Give start_time for a scheduled meeting, or omit it for one that can be joined right now. This does NOT put anything in a calendar or invite anyone: send the join_url to the participants, or use calendar.create_event with online_meeting_provider='zoom' to also book it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "meetings_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesMeeting title shown to participants.
agendaNoShort description shown in the invitation.
providerNoMeeting provider. Only 'zoom' for now.zoom
timezoneNoIANA timezone the start_time (without offset) is in, e.g. 'Europe/Berlin'.
start_timeNoStart in ISO 8601 (e.g. 2026-12-15T14:00:00). Without an offset it is read in `timezone`. OMIT for a meeting joinable right now.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
zoom_account_idNoWhich connected Zoom account hosts it. Only needed when the workspace has several; one account is used automatically.
duration_minutesNoPlanned length in minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With readOnlyHint=false and openWorldHint=true already declared, the description still adds substantial behavior: the tool refuses when Zoom is not connected, meetings have no waiting room so anyone with the link enters directly, and the output includes a join_url the caller must distribute itself. These are operational facts not recoverable from the annotations.

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?

Front-loaded with what it creates and returns, then prerequisites, then scheduling, then the calendar disambiguation. Five sentences, none redundant; even the no-waiting-room note carries real access-control meaning.

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

Completeness5/5

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

No output schema exists, and the description fills that gap by naming the returned join_url and telling the caller what to do with it. Combined with prerequisite handling and sibling disambiguation, nothing an agent needs to invoke this correctly is missing.

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 topic, agenda, timezone, start_time, zoom_account_id, duration_minutes and in_workspace are all documented in the schema itself. The description restates the start_time scheduled-vs-instant distinction rather than adding new semantics, so the baseline 3 applies.

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?

Specific verb + resource + scope: 'Create an online video meeting on the workspace's own Zoom account and get its join link.' It also explicitly distinguishes itself from calendar.create_event, so an agent can separate it from the calendar-creation sibling without opening either schema.

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

Usage Guidelines5/5

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

States the prerequisite ('Needs the workspace's Zoom connected'), the remedy if unmet (channels.connect with channel='zoom'), the alternative path (calendar.create_event with online_meeting_provider='zoom' to also book it), and an explicit exclusion ('does NOT put anything in a calendar or invite anyone'). When-to-use and when-not-to-use are both covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.