Skip to main content
Glama

generate_meeting_link

Create a one-off virtual meeting link (Zoom, Google Meet, etc.) via a connected provider. Use this when a standalone meeting URL is needed without a full interview event.

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": {
      "provider": "<provider>",
      "topic": "<topic>"
    },
    "name": "generate_meeting_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesMeeting title or topic.
durationNoMeeting length in minutes.
providerYesThe connected provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / duration / default
      Added value: +60
    • changedInput schema / properties / duration / description
      Previous value: -"Duration in minutes (default 60)"New value: +"Meeting length in minutes."
    • changedInput schema / properties / provider / description
      Previous value: -"Meeting provider (Calendly or Cal.com)"New value: +"The connected provider."
    • changedInput schema / properties / topic / description
      Previous value: -"Meeting topic/title"New value: +"Meeting title or topic."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that a connected provider is required and that the link is one-off, but says nothing about whether the link expires, who can join, or what the response contains.

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, zero padding, with the purpose front-loaded and the usage condition immediately after. Every clause earns its place.

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?

For a three-parameter tool with full schema coverage and no output schema, the description covers purpose, prerequisite, and scope adequately. The main omission is any hint about what is returned (a URL string vs. an object), which matters for chaining into downstream steps.

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 all three parameters are already documented, establishing a baseline of 3. The only added color is "Zoom, Google Meet, etc.," which actually diverges from the enum values (calendly, calcom) and adds no usable detail about provider selection.

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?

States a specific verb and resource ("create a one-off virtual meeting link") and explicitly scopes it against a nearby capability: a standalone URL "without a full interview event." An agent can distinguish this from interview-creation tools without inspecting the schema.

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?

Gives a clear triggering condition ("Use this when a standalone meeting URL is needed without a full interview event"), which implicitly excludes the interview-event path. It does not name the alternative tool outright, so the routing is inferential rather than explicit.

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.

Resources