Skip to main content
Glama
EoinFalconer

Granola MCP Server

by EoinFalconer

get_meeting_details

Retrieve detailed meeting information including notes, transcripts, and organization data from Granola.ai meeting intelligence platform using a meeting ID.

Instructions

Get detailed information about a specific meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_idYesMeeting ID to retrieve details for

Implementation Reference

  • Complete implementation of get_meeting_details tool including schema registration (name, description, parameters) and execute handler function that retrieves meeting details from cache and formats them
    // Tool: get_meeting_details
    server.addTool({
      name: 'get_meeting_details',
      description: 'Get detailed information about a specific meeting',
      parameters: z.object({
        meeting_id: z.string().describe('Meeting ID to retrieve details for')
      }),
      execute: async ({ meeting_id }) => {
        await ensureDataLoaded();
    
        const doc = documentsCache.get(meeting_id);
        if (!doc) {
          return `Meeting '${meeting_id}' not found`;
        }
    
        const details: string[] = [
          `# Meeting Details: ${getTitle(doc)}\n`,
          `**ID:** ${doc.id}`,
          `**Date:** ${formatDate(doc.created_at)}`,
          `**Updated:** ${formatDate(doc.updated_at)}`
        ];
    
        if (doc.workspace_name) {
          details.push(`**Workspace:** ${doc.workspace_name}`);
        }
    
        if (doc.folders && doc.folders.length > 0) {
          const folderNames = doc.folders.map(f => f.name).join(', ');
          details.push(`**Folders:** ${folderNames}`);
        }
    
        if (doc.people && doc.people.length > 0) {
          const people = doc.people.map(p => p.name).join(', ');
          details.push(`**Participants:** ${people}`);
        }
    
        return details.join('\n');
      }
    });
  • Input parameter schema definition using Zod - requires a meeting_id string parameter
    parameters: z.object({
      meeting_id: z.string().describe('Meeting ID to retrieve details for')
    }),
  • GranolaDocument interface type definition that defines the structure of meeting data retrieved and displayed by get_meeting_details
    export interface GranolaDocument {
      id: string;
      title: string;
      created_at: string;
      updated_at: string;
      workspace_id?: string;
      workspace_name?: string;
      folders?: FolderInfo[];
      last_viewed_panel?: DocumentPanel;
      people?: Array<{ name: string }>;
      [key: string]: any;
    }
  • ensureDataLoaded and loadData helper functions that populate the documentsCache with meeting data before the tool executes
    async function ensureDataLoaded() {
      const now = Date.now();
      if (documentsCache.size === 0 || (now - lastFetchTime) > CACHE_TTL) {
        await loadData();
      }
    }
    
    /**
     * Load data from Granola API
     */
    async function loadData() {
      console.error('Fetching data from Granola API...');
      
      const data = await apiClient.getAllDocumentsWithMetadata();
      
      if (!data) {
        console.error('Failed to fetch data from API');
        return;
      }
    
      // Update caches
      documentsCache.clear();
      for (const doc of data.documents) {
        documentsCache.set(doc.id, doc);
      }
      workspacesCache = data.workspaces;
      foldersCache = data.documentLists;
      lastFetchTime = Date.now();
    
      console.error(`Loaded ${documentsCache.size} documents from API`);
    }
  • Helper functions formatDate and getTitle used by get_meeting_details to format meeting dates and extract titles safely
    /**
     * Format date in local timezone
     */
    function formatDate(dateStr: string | null | undefined): string {
      if (!dateStr) return 'Unknown date';
      try {
        const date = new Date(dateStr);
        return date.toLocaleString('en-US', {
          year: 'numeric',
          month: '2-digit',
          day: '2-digit',
          hour: '2-digit',
          minute: '2-digit',
          hour12: false
        });
      } catch {
        return dateStr;
      }
    }
    
    /**
     * Safe string for searching (handles null/undefined)
     */
    function safeString(str: string | null | undefined): string {
      return str || '';
    }
    
    /**
     * Get document title safely
     */
    function getTitle(doc: GranolaDocument): string {
      return doc.title || 'Untitled Meeting';
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details but doesn't specify what 'detailed information' includes, whether it's read-only, if it requires authentication, or any rate limits. This leaves significant gaps in understanding the tool's behavior beyond basic retrieval.

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, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly, earning a top score for conciseness.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines, behavioral traits, and output format, which are needed for full contextual understanding, resulting in a score of 3 as the minimum viable.

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 has 100% description coverage, with the 'meeting_id' parameter clearly documented. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline score of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific meeting'), making it easy to understand what the tool does. However, it doesn't differentiate from sibling tools like 'get_meeting_content' or 'search_meetings', which could have overlapping functionality, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_meeting_content' and 'search_meetings' available, it doesn't specify if this is for metadata retrieval, when to choose it over other tools, or any prerequisites, leaving the agent to guess based on context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EoinFalconer/granola-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server