Skip to main content
Glama
Sign In
Granola MCP Server

Granola MCP Server

by twanlass
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_document

Retrieve a Granola document's AI-generated notes by document ID, or request the raw meeting transcript instead.

Instructions

Get the content for a specific Granola document. Returns AI-generated notes by default, or raw transcript if requested.

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": {
      "document_id": "<document_id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
transcriptNoIf true, return raw transcript instead of AI notes (default: false)
document_idYesThe ID of the document to fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It does disclose the default behavior (AI-generated notes) and the transcript option, which adds value. However, it does not mention error cases, permissions, or return format details, leaving some gaps.

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?

The description is a single, front-loaded sentence that clearly states the action, resource, and key options. Every word earns its place, with zero fluff.

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?

For a simple two-parameter retrieval tool, the description is reasonably complete. It explains the purpose and the key behavioral choice, though it does not explicitly note the read-only nature or what happens when a document is not found.

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%, so the baseline is 3. The description references the transcript parameter ('raw transcript if requested') but adds no meaning beyond the schema's existing descriptions of document_id and transcript.

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 a specific verb and resource: 'Get the content for a specific Granola document.' This distinguishes it from siblings like get_recent_documents (list) and search_documents (find).

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?

The phrase 'specific Granola document' implies the user must already have a document ID, making the context clear. However, it does not explicitly state when to use this over get_recent_documents or search_documents, nor provide exclusions.

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