Skip to main content
Glama

Outil.io

Create zoom meeting

create_zoom_meeting

Créer une vraie réunion Zoom avec le compte connecté au projet. Retourne son identifiant et son lien de participation. Nécessite le rôle éditeur ou supérieur.

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>",
      "startsAt": "<startsAt>",
      "durationMinutes": "<durationMinutes>"
    },
    "name": "create_zoom_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
agendaNo
startsAtYes
timezoneNo
durationMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations (openWorldHint=true, destructiveHint=false), the description discloses two important behaviors: the meeting is created on the real connected Zoom account (external side effect) and the call returns an identifier and a join link. It also adds an authorization requirement (editor role or above) that annotations do not cover. It stops short of describing quota, scheduling conflicts, or idempotency behavior.

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?

Three short sentences, front-loaded with the action, then the return value, then the permission prerequisite. No filler, and each sentence contributes distinct information.

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

Completeness3/5

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

The description covers the side effect, the return payload (ID and join link, which substitutes for the absent output schema), and the permission requirement. However, for a five-parameter creation tool with zero schema description coverage, the total absence of parameter explanation leaves the definition only minimally sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate and does not: it never mentions topic, startsAt, durationMinutes, timezone, or agenda, nor any format expectations. The schema carries constraints (min/max lengths, 5–1440 minutes) but leaves parameter meaning undocumented in both places.

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

Purpose4/5

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

The description states a specific verb and resource ('Créer une vraie réunion Zoom') and clarifies that it operates on the account connected to the project, which distinguishes it from a purely local/simulated object and from delete_zoom_meeting. It is clear, though it does not explicitly contrast itself with any other creation sibling.

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?

It gives a prerequisite (editor role or higher) and implies when the tool applies by saying it creates a real Zoom meeting on the connected account, but there is no explicit when-to-use vs when-not-to-use guidance or mention of alternative tools. Usage is therefore implied rather than routed.

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.