Google Calendar and Meet MCP Server

meet_v2_get_participant

Retrieve specific participant details from Google Meet conferences using the Meet API v2, enabling attendance tracking and meeting moderation.

Instructions

[Meet API v2 GA] Get details of a specific participant

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": {
      "participant_name": "<participant_name>"
    },
    "name": "meet_v2_get_participant"
  }
}

Input Schema

Name	Required	Description	Default
`participant_name`	Yes	Name of the participant (conferenceRecords/{record_id}/participants/{participant_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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get details'), but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'details' entail (e.g., participant metadata, status). This leaves significant gaps for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the API version and core purpose. It avoids unnecessary words, though it could be slightly more informative without sacrificing brevity, such as hinting at the type of details returned.

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 complexity of a participant retrieval tool with no annotations and no output schema, the description is insufficient. It lacks details on return values, error cases, or behavioral traits, making it incomplete for effective agent use without additional 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 'participant_name' fully documented in the schema. The description doesn't add any additional meaning beyond what the schema provides, such as format examples or usage notes, but the high schema coverage justifies the baseline score of 3.

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 ('Get details') and target ('a specific participant'), specifying it's for the Meet API v2 GA. However, it doesn't distinguish this tool from its sibling 'meet_v2_get_participant_session', which also retrieves participant-related data but for sessions, leaving some ambiguity in sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'meet_v2_list_participants' or 'meet_v2_get_participant_session'. The description implies usage for a specific participant but offers no context on prerequisites, error conditions, or comparative scenarios with sibling tools.

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