Skip to main content
Glama

Send the MeetNotes Notetaker to a call

meetnotes_invite_notetaker

Use this when the user shares a Google Meet, Zoom or Microsoft Teams link and wants the call recorded, transcribed or turned into minutes and action items. Invites the MeetNotes Notetaker into the call from its link — now, or at join_at. It joins as a visible participant named "MeetNotes Notetaker"; the host must admit it from the waiting room. It records until the call ends; the recording is then transcribed like any other and spends the account's minutes. Returns a job receipt with a job_id at once; the job reports the meeting id once the call has ended, and the minutes once processing completes. The same link while an invitation is active returns that invitation with deduplicated true. At most 2 active invitations per account. Leaving early or cancelling a booking is done from the MeetNotes app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoMeeting title; when omitted the minutes name it.
join_atNoISO 8601 time to join. Omitted or in the past means now; at most 7 days ahead.
languageNoLanguage mainly spoken, as a name or BCP-47 tag. Omitted, the account's own preference applies.
meeting_urlYesThe Meet, Zoom or Teams link — or the joining text it was pasted in.
output_languageNoThe language the user is writing in; the minutes are written in it. A BCP-47 tag or a plain language name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
kindYes
job_idYes
statusYes
join_atYes
platformYes
meeting_idYesNull until the call has ended and the recording is being processed.
deduplicatedYes
next_poll_after_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations: discloses the visible participant identity, the waiting-room admission requirement, that recording runs until call end, that it spends account minutes, the async receipt/job_id flow, the deduplicated-response behavior, and the 2-active-invitation cap. These are exactly the operational traits an agent needs beyond readOnlyHint=false and destructiveHint=false.

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?

Front-loaded with the triggering scenario, then behavior, then return contract. Dense but every sentence carries information; only the app-routing sentence is marginal. Slightly long for a single tool but not padded.

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

Completeness5/5

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

For a write tool with an output schema, it still explains the async lifecycle (immediate job_id, later meeting id, then minutes) and the invite cap, so an agent knows both what it gets back and what constraints apply. Nothing required for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is already 100%, so baseline is 3. The description adds real meaning beyond the schema: join_at can mean 'now' when omitted or past, meeting_url may be raw joining text pasted around the link, and output_language governs the language minutes are written in.

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?

States a specific verb+resource ('Invites the MeetNotes Notetaker into the call from its link') and names the trigger condition (user shares a Meet/Zoom/Teams link wanting recording, transcription, or minutes). An agent can distinguish it from siblings like meetnotes_import_audio or meetnotes_get_transcript without opening schemas.

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

Usage Guidelines4/5

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

Clear context for when to invoke: user shares a call link and wants it recorded/transcribed/summarized. It also discloses the dedup path and notes that leaving early or cancelling a booking happens in the MeetNotes app (routing away from this tool), but it does not name a concrete alternative tool for adjacent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources