Skip to main content
Glama
Sign In
Granola MCP Server

Granola MCP Server

by twanlass
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_recent_documents

List recent Granola meeting documents to access meeting notes and transcripts. Use the limit parameter to control the number of results.

Instructions

Get a list of recent Granola meeting documents

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of documents to fetch (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 burden of behavioral disclosure. It states the tool 'gets' a list, implying a read-only operation, but provides no details about ordering, pagination, authentication, or potential errors. This is minimal disclosure and leaves significant ambiguity for an agent.

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, clear sentence with no redundancy or filler. It effectively communicates the tool's purpose while remaining concise, making it easy for an agent to parse.

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

Completeness3/5

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

The tool is simple (one optional parameter, no output schema), so the description covers the essential purpose. However, it lacks any indication of return format, ordering, or disambiguation from sibling tools, which a fuller description could provide. It is minimally viable but has clear gaps.

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?

The input schema provides a 100% description coverage for the only parameter (limit), so the baseline is 3. The description adds no additional parameter semantics, but that is acceptable given the schema already documents the parameter fully.

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 uses a specific verb ('Get') and a specific resource ('recent Granola meeting documents'), clearly distinguishing it from siblings like get_document (which likely fetches a single document) and search_documents (which searches). The scope is clear and unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or scenarios where search_documents or get_document would be more appropriate. The description is purely functional with no contextual advice.

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