Skip to main content
Glama

get_meeting

Fetch a single meeting as Markdown with metadata, summary, and transcript, using transcript windows and continuation values to handle long records.

Instructions

Fetch one meeting as markdown. Sections: metadata, summary, transcript. A long transcript comes in windows of max_characters; a cut window ends with the transcript_from value that continues it.

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": {
      "id": "<id>"
    },
    "name": "get_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesShort id from list_meetings, full UUID, or "latest".
includeNoComma-separated subset of metadata,summary,transcript. Default: all three.
max_charactersNoTranscript characters per call (default 40,000, maximum 200,000).
transcript_fromNoOptional HH:MM:SS; the transcript starts at the first line at or after it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers the key non-obvious trait: long transcripts are returned in windows bounded by max_characters, and a truncated window hands back a transcript_from value for continuation. That continuation contract is genuine behavioral disclosure that neither annotations nor schema provide. It stops short of error/fallback behavior for bad ids or the "latest" shorthand.

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?

Two sentences, zero filler, and the output format and section list are front-loaded before the windowing detail. Every clause contributes either scope or behavior.

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

Completeness4/5

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

No output schema or annotations exist, so the description must cover returns itself, and it does: markdown format, three named sections, and chunked-transcript mechanics. Only edge cases (invalid id, what "latest" resolves to, whether a cut window is signalled in the text) are left unaddressed.

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 100%, so the baseline is 3, but the description adds real meaning by explaining how max_characters and transcript_from relate as a pagination pair rather than two independent fields. That linkage is not expressed in the individual parameter descriptions.

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?

"Fetch one meeting as markdown" names a specific verb and a single-resource scope, which distinguishes it from list_meetings and search_meetings by cardinality. It also enumerates the returned sections, so an agent knows what it gets before calling.

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?

Usage is only implied: the schema's id field points at list_meetings, so the discovery-then-fetch flow is inferable, but the description never says when to prefer this over search_meetings or get_timeline. No exclusions or prerequisites are stated in the description itself.

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