Skip to main content
Glama
iTvX

Google Workspace MCP — Gmail edition

by iTvX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_meet

Browse and manage Google Meet conferences: list meetings, participants, transcripts, recordings, and smart notes; create spaces and end active calls.

Instructions

Browse past Google Meet conferences, participants, transcripts, recordings, and AI-generated smart notes. Requires Workspace Business Standard+ for transcripts/recordings.

Input Schema

NameRequiredDescriptionDefault
emailYesAccount email address. On list operations, "all" runs it once for every configured account.
spaceNoMeeting code (the abc-mnop-xyz part of a Meet link) or a full spaces/... resource name
filterNoEBNF filter. On `listConferences`, e.g. 'space.meeting_code = "abc-mnop-xyz"' or 'start_time>="2026-01-01T00:00:00Z"'. On `listParticipants`, e.g. 'latest_end_time IS NULL' for active participants.
operationYeslistConferences: list recent meeting conferences (default: descending by start time) | getConference: get details of a specific conference | listParticipants: list who attended a conference | listTranscripts: list transcripts for a conference (requires Workspace Business Standard+) | getTranscript: get transcript metadata including Google Docs destination | listTranscriptEntries: get structured transcript text — who said what, with timestamps | listRecordings: list recordings for a conference (saved as MP4 in Drive) | getRecording: get recording metadata including Drive file ID and playback link | getFullTranscript: get the full who-said-what transcript for a conference (chains transcripts + entries + participant names automatically). Use pageToken to continue reading. | listSmartNotes: list Gemini-generated smart notes for a conference | getSmartNote: get smart note metadata including Google Docs destination | createSpace: create a standalone Google Meet link (not attached to a calendar event) | activeConferences: list conferences happening RIGHT NOW across your meetings | getSpace: look up a meeting space by its meeting code or resource name | updateSpace: change who can join a meeting space, or turn host controls on or off | endActiveConference: end the call happening in a space right now, disconnecting everyone in it
pageTokenNoPage token from a previous getFullTranscript call to continue reading
accessTypeNoWho can join without knocking. OPEN: anyone with the link. TRUSTED (default): people in your organization, plus invited guests. RESTRICTED: invited guests only.
maxResultsNoMax results per page, as default/ceiling. Differs by operation: `listConferences` 25/100, `listParticipants` 100/250, `listTranscriptEntries` 100/100. (Google's own default for transcript entries is 10; this tool raises it.)
moderationNoTurn on host controls — the host admits guests and manages who can present or chat.
conferenceIdNoConference record ID (from `listConferences`)
recordingNameNoRecording resource name (from listRecordings)
smartNoteNameNoSmart note resource name (from listSmartNotes)
transcriptNameNoTranscript resource name (from `listTranscripts`, e.g. conferenceRecords/.../transcripts/...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.8.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly fails: it says 'browse past' conferences, yet the tool can create spaces and end an active call (disconnecting everyone) — a significant side effect that is never flagged. The licensing requirement is the one real disclosure; permissions, reversibility of updateSpace, and read-vs-write nature of each operation are absent.

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?

Two sentences, front-loaded with scope and then the prerequisite — no filler. It is arguably undersized for a 17-operation tool, but every sentence present earns its place and nothing is padded.

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?

For a 12-parameter tool with 17 operations, no annotations, and no output schema, the description covers only the read/inspection half of the surface. It omits the createSpace/updateSpace/endActiveConference mutations and their consequences, leaving an agent unable to anticipate the tool's write behaviors from the description alone.

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%, including detailed per-operation explanations, filter examples, and per-operation page-size limits, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond the licensing note, making the baseline 3 appropriate.

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 names a specific resource domain (Google Meet conferences, participants, transcripts, recordings, smart notes) with the verb 'browse', so an agent knows broadly what it covers. However, it frames the tool as purely read-oriented while the schema includes mutation operations such as createSpace, updateSpace, and endActiveConference, so the stated purpose is narrower than the tool's actual scope.

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

Usage Guidelines3/5

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

It gives one concrete prerequisite — transcripts/recordings require Workspace Business Standard+ — which is genuinely useful usage context. But there is no guidance on when to pick manage_meet over siblings like manage_calendar or manage_workspace, nor any exclusion conditions, so usage is only implied.

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