Skip to main content
Glama

get_meeting_transcript

Retrieve the full transcript of a specific meeting by providing its meeting ID, giving access to speaker-identified conversations and meeting details.

Instructions

Get transcript for a specific meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_idYesMeeting ID to get transcript for

Implementation Reference

  • The _get_meeting_transcript method that executes the tool logic for retrieving a meeting transcript, formats it with speaker info, language, confidence, and content.
    async def _get_meeting_transcript(self, meeting_id: str) -> List[TextContent]:
        """Get meeting transcript."""
        if not self.cache_data:
            return [TextContent(type="text", text="No meeting data available")]
        
        if meeting_id not in self.cache_data.transcripts:
            return [TextContent(type="text", text=f"No transcript available for meeting '{meeting_id}'")]
        
        transcript = self.cache_data.transcripts[meeting_id]
        meeting = self.cache_data.meetings.get(meeting_id)
        
        output = [f"# Transcript: {meeting.title if meeting else meeting_id}\n"]
        
        if transcript.speakers:
            output.append(f"**Speakers:** {', '.join(transcript.speakers)}")
        
        if transcript.language:
            output.append(f"**Language:** {transcript.language}")
        
        if transcript.confidence:
            output.append(f"**Confidence:** {transcript.confidence:.2%}")
        
        output.append("\n## Transcript Content\n")
        output.append(transcript.content)
        
        return [TextContent(type="text", text="\n".join(output))]
  • Registration of the get_meeting_transcript tool in the list_tools() handler with input schema requiring meeting_id.
    Tool(
        name="get_meeting_transcript",
        description="Get transcript for a specific meeting",
        inputSchema={
            "type": "object",
            "properties": {
                "meeting_id": {
                    "type": "string", 
                    "description": "Meeting ID to get transcript for"
                }
            },
            "required": ["meeting_id"]
        }
    ),
  • The call_tool dispatcher that routes the 'get_meeting_transcript' tool name to the _get_meeting_transcript handler method.
    elif name == "get_meeting_transcript":
        return await self._get_meeting_transcript(arguments["meeting_id"])
  • The MeetingTranscript Pydantic model used as the schema for transcript data, containing meeting_id, content, speakers, language, and confidence fields.
    class MeetingTranscript(BaseModel):
        """Meeting transcript information."""
        meeting_id: str
        content: str
        speakers: List[str] = []
        language: Optional[str] = None
        confidence: Optional[float] = None
  • The CacheData model that stores transcripts in a dictionary keyed by meeting_id, used by the handler to look up transcripts.
    class CacheData(BaseModel):
        """Complete cache data structure."""
        meetings: Dict[str, MeetingMetadata] = {}
        documents: Dict[str, MeetingDocument] = {}
        transcripts: Dict[str, MeetingTranscript] = {}
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as read-only nature, required permissions, error conditions, or return format.

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 that is front-loaded and to the point. No redundant words, so every word earns its place.

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 simplicity (one parameter, no output schema), the description is minimally adequate. However, it lacks any behavioral context that could help an agent handle errors or understand return data.

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 coverage is 100%, but the parameter description ('Meeting ID to get transcript for') adds little beyond the parameter name. Baseline 3 due to high coverage, no extra meaning added.

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 the verb 'Get' and specific resource 'transcript for a specific meeting', distinguishing it from siblings like get_meeting_details (details) and get_meeting_documents (documents).

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 or not use the tool, no mention of alternatives like search_meetings for finding meetings. Usage is only implied by the action.

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