Skip to main content
Glama

get_meeting_documents

Retrieve all documents associated with a meeting using its meeting ID. Access notes, slides, and attachments from Granola.ai meeting intelligence records.

Instructions

Get documents associated with a meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_idYesMeeting ID to get documents for

Implementation Reference

  • Handler function that retrieves documents for a given meeting_id from the cache, formats them with title, type, creation time, tags, and content, and returns as TextContent.
    async def _get_meeting_documents(self, meeting_id: str) -> List[TextContent]:
        """Get meeting documents."""
        if not self.cache_data:
            return [TextContent(type="text", text="No meeting data available")]
        
        documents = [doc for doc in self.cache_data.documents.values() 
                    if doc.meeting_id == meeting_id]
        
        if not documents:
            return [TextContent(type="text", text=f"No documents found for meeting '{meeting_id}'")]
        
        meeting = self.cache_data.meetings.get(meeting_id)
        output = [f"# Documents: {meeting.title if meeting else meeting_id}\n"]
        output.append(f"Found {len(documents)} document(s):\n")
        
        for doc in documents:
            output.append(f"## {doc.title}")
            output.append(f"**Type:** {doc.document_type}")
            output.append(f"**Created:** {self._format_local_time(doc.created_at)}")
            
            if doc.tags:
                output.append(f"**Tags:** {', '.join(doc.tags)}")
            
            output.append(f"\n{doc.content}\n")
            output.append("---\n")
        
        return [TextContent(type="text", text="\n".join(output))]
  • Tool registration with name 'get_meeting_documents', description, and input schema requiring a meeting_id string.
    Tool(
        name="get_meeting_documents",
        description="Get documents associated with a meeting",
        inputSchema={
            "type": "object",
            "properties": {
                "meeting_id": {
                    "type": "string",
                    "description": "Meeting ID to get documents for" 
                }
            },
            "required": ["meeting_id"]
        }
    ),
  • Input schema for the tool: a JSON object with a required 'meeting_id' string field.
    inputSchema={
        "type": "object",
        "properties": {
            "meeting_id": {
                "type": "string",
                "description": "Meeting ID to get documents for" 
            }
        },
        "required": ["meeting_id"]
    }
  • Call routing in the call_tool handler that dispatches 'get_meeting_documents' to the _get_meeting_documents method.
    elif name == "get_meeting_documents":
        return await self._get_meeting_documents(arguments["meeting_id"])
  • Pydantic model defining the MeetingDocument schema used by the handler to access document fields (title, content, document_type, created_at, tags, meeting_id).
    class MeetingDocument(BaseModel):
        """Meeting document information."""
        id: str
        meeting_id: str
        title: str
        content: str
        document_type: str
        created_at: datetime
        tags: List[str] = []
Behavior2/5

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

No annotations provided; description only states what it does but not behavioral traits like read-only nature, permissions needed, or rate limits.

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?

Single sentence, no fluff; front-loaded with purpose, but could be slightly more detailed without losing conciseness.

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

Completeness2/5

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

Simple tool with one parameter but no output schema; description lacks details about return format or content, which is needed for agent to use it effectively.

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 baseline is 3; description adds no extra meaning beyond the schema's parameter description.

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 verb 'Get' and resource 'documents associated with a meeting', making it distinct from siblings like get_meeting_details or get_meeting_transcript.

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 on when to use this tool versus alternatives; no comparison to siblings or mention of prerequisites.

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/maxgerlach1/granola-ai-mcp-server'

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