Skip to main content
Glama

graph_create_online_meeting

Create a Microsoft Teams online meeting and return the join link to share; schedule a standalone meeting without adding a calendar event.

Instructions

Create a Teams online meeting and get its join link.

The joinWebUrl field in the response is the link to share. This creates a meeting without a calendar event; use graph_create_event with is_online_meeting for a meeting that also appears on calendars. Needs the OnlineMeetings.ReadWrite permission.

Args: subject: Meeting subject. start_datetime: Start time in ISO 8601 with an offset or Z (e.g. "2026-03-01T10:00:00Z"). end_datetime: End time in ISO 8601 with an offset or Z. attendees: Optional list of attendee email addresses or user IDs. allowed_presenters: Who can present: "everyone", "organization", "roleIsPresenter", or "organizer" (default "everyone").

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": {
      "subject": "<subject>",
      "start_datetime": "<start_datetime>",
      "end_datetime": "<end_datetime>"
    },
    "name": "graph_create_online_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectYes
attendeesNo
end_datetimeYes
start_datetimeYes
allowed_presentersNoeveryone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that no calendar event is created, names the required OnlineMeetings.ReadWrite permission, and points at joinWebUrl as the shareable artifact. It does not say whether attendees receive invitations or whether repeated calls create duplicate meetings, which matters for a creation tool.

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 the highest-value fact (joinWebUrl is the link to share), then the sibling distinction, then the permission, then per-argument notes. Each sentence adds information; nothing is padding.

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 no-annotation, no-output-schema creation tool this covers the essentials: what it makes, what it returns, the auth requirement, and all parameter formats. The remaining gap is post-creation behavior toward attendees and the shape of the rest of the response beyond joinWebUrl.

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

Parameters5/5

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

Schema coverage is 0%, so the description must do all the work, and it documents every one of the five parameters: subject, ISO 8601 datetime format with an example, attendee list accepting emails or user IDs, and the presenter enum with its default. The enum is restated from the schema but gains meaning from the "who can present" framing.

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 opens with a specific verb and resource ("Create a Teams online meeting") plus the concrete payoff ("get its join link"). It also explicitly contrasts itself with graph_create_event, so an agent can distinguish the two 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?

It states the selection rule plainly: this creates a meeting with no calendar event, whereas graph_create_event with is_online_meeting is for meetings that appear on calendars. That is an explicit when-to-use-this-instead-of-that condition, not an implied one.

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

Deploy Server

Other Tools