Skip to main content
Glama
Sign In
Granola MCP Server

Granola MCP Server

by NimbleBrainInc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_meeting

Get complete meeting details including notes, summaries, and optional transcript by providing the meeting ID.

Instructions

Get complete meeting details including notes and summaries.

Args: meeting_id: Meeting document ID include_transcript: Include full transcript in notes_plain field ctx: MCP context

Returns: Full meeting details with notes, attendees, and AI panels

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

Input Schema

NameRequiredDescriptionDefault
meeting_idYes
include_transcriptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the tool 'gets' data, omitting details like required permissions, data freshness, side effects, or response size. This is insufficient for understanding the tool's full behavior.

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 presented in a clear docstring-like format with Args and Returns sections, making it easy to scan. However, it includes an undocumented 'ctx' parameter (likely MCP context) that adds minor clutter. Overall, it is concise and well-structured.

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?

Given the presence of an output schema, the description adequately covers the tool's purpose and parameters. It lacks guidance on usage context relative to sibling tools, but for a simple retrieval tool with good schema support, it is mostly complete.

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?

The schema has 0% description coverage, but the description adds meaningful context for both parameters: 'meeting_id: Meeting document ID' and 'include_transcript: Include full transcript in notes_plain field'. This goes beyond the bare schema, though the 'ctx' parameter is undocumented and might confuse.

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?

The description clearly states 'Get complete meeting details including notes and summaries', using a specific verb and resource. It effectively distinguishes itself from sibling tools like list_meetings, get_transcript, and get_meeting_stats.

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?

The description implies usage when full meeting details are needed, but lacks explicit guidance on when to use this tool vs alternatives, such as when to use get_transcript or list_meetings instead. No 'when not to use' or alternative recommendations are provided.

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