Google Calendar and Meet MCP Server

meet_v2_end_active_conference

End the active conference in a Google Meet space using the Meet API v2 to close ongoing meetings and manage meeting sessions.

Instructions

[Meet API v2 GA] End the active conference in a Google Meet space

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": {
      "space_name": "<space_name>"
    },
    "name": "meet_v2_end_active_conference"
  }
}

Input Schema

Name	Required	Description	Default
`space_name`	Yes	Name of the space (spaces/{space_id})

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?

No annotations are provided, so the description carries full burden. It mentions 'End the active conference,' implying a destructive action, but fails to disclose critical behavioral traits like required permissions, whether the action is reversible, effects on participants, or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 action ('End the active conference') and includes relevant context ('Meet API v2 GA'). There is no wasted verbiage, making it appropriately sized and well-structured for quick comprehension.

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 as a destructive operation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral outcomes, error handling, or return values, which are crucial for safe invocation. The high schema coverage doesn't compensate for these gaps in a mutation context.

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 description coverage is 100%, with the parameter 'space_name' fully documented in the schema. The description adds no additional meaning beyond the schema, such as format examples or constraints. With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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 ('End') and target ('active conference in a Google Meet space'), specifying it's for the Meet API v2 GA. It distinguishes from siblings like meet_v2_get_conference_record or meet_v2_list_conference_records by focusing on termination rather than retrieval. However, it doesn't explicitly differentiate from other destructive tools like meet_v2_update_space, keeping it at a 4.

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, such as meet_v2_update_space for modifying a space instead of ending a conference, or prerequisites like needing an active conference. It lacks explicit when/when-not instructions or named alternatives, resulting in minimal usage context.

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