Google Calendar and Meet MCP Server

meet_v2_create_space

Create a Google Meet space with advanced configuration options including access controls, recording, transcription, smart notes, attendance reports, moderation, and participant restrictions.

Instructions

[Meet API v2 GA] Create a Google Meet space with advanced configuration

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "meet_v2_create_space"
  }
}

Input Schema

Name	Required	Description
`access_type`	No	Access type for the space (default: TRUSTED)
`enable_recording`	No	Enable automatic recording (requires Google Workspace Business Standard+)
`enable_transcription`	No	Enable automatic transcription (requires Google Workspace)
`enable_smart_notes`	No	Enable automatic smart notes with Gemini (requires Gemini license)
`attendance_report`	No	Enable attendance report generation
`moderation_mode`	No	Enable moderation for the space (default: OFF)
`chat_restriction`	No	Chat restriction level (default: NO_RESTRICTION)
`present_restriction`	No	Presentation restriction level (default: NO_RESTRICTION)
`default_join_as_viewer`	No	Join participants as viewers by default (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a space but lacks critical details: whether this is a mutating operation (implied by 'Create'), what permissions or licenses are needed beyond the parameter hints, potential side effects (e.g., resource limits), or what the output looks like. The mention of 'advanced configuration' is vague and doesn't compensate for the missing behavioral context.

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?

The description is a single, efficient sentence that front-loads the key information: API version ('Meet API v2 GA'), action ('Create'), resource ('Google Meet space'), and scope ('with advanced configuration'). There's no wasted verbiage, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the tool's complexity (9 parameters, creation operation) and lack of annotations and output schema, the description is insufficient. It doesn't address behavioral aspects like mutation effects, error conditions, or return values, leaving significant gaps for an agent to understand how to use the tool effectively in practice.

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?

The input schema has 100% description coverage, with each parameter well-documented (e.g., defaults, requirements like 'requires Google Workspace'). The description adds no additional parameter semantics beyond the schema, so it meets the baseline of 3 where the schema does the heavy lifting. However, it doesn't explain how parameters interact or their overall impact on the created space.

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 clearly states the action ('Create') and resource ('Google Meet space'), and specifies 'with advanced configuration' which hints at the tool's scope. However, it doesn't explicitly differentiate from sibling tools like 'meet_v2_update_space' or 'calendar_v3_create_event', which would require a more specific distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication requirements), compare it to other creation tools in the sibling list, or indicate scenarios where it's preferred over simpler options. This leaves the agent without context for tool selection.

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