Skip to main content
Glama
btn0s

Granola MCP Server

by btn0s

get_granola_transcript

Retrieve a specific meeting transcript using its unique ID to access recorded discussions and content from the Granola platform.

Instructions

Get a specific Granola transcript by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe transcript ID to retrieve

Implementation Reference

  • Handler for the 'get_granola_transcript' tool. Extracts ID from arguments, fetches the document using GranolaApiClient, validates it's a meeting transcript, converts ProseMirror content to markdown, and returns formatted JSON response.
    case "get_granola_transcript": {
      const id = args?.id as string;
      const doc = await apiClient.getDocumentById(id);
      if (!doc || doc.type !== "meeting") {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                error: `Transcript with id ${id} not found`,
              }),
            },
          ],
          isError: true,
        };
      }
    
      let markdown = "";
      if (doc.last_viewed_panel?.content) {
        markdown = convertProseMirrorToMarkdown(
          doc.last_viewed_panel.content
        );
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                id: doc.id,
                meeting_id: doc.id,
                title: doc.title,
                content: markdown,
                created_at: doc.created_at,
                updated_at: doc.updated_at,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • src/index.ts:122-135 (registration)
    Registration of the 'get_granola_transcript' tool in the tools array used for ListToolsRequestHandler. Includes name, description, and input schema requiring a string 'id'.
    {
      name: "get_granola_transcript",
      description: "Get a specific Granola transcript by its ID.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "The transcript ID to retrieve",
          },
        },
        required: ["id"],
      },
    },
  • Helper method in GranolaApiClient to retrieve a specific Granola document (transcript) by its ID, fetched from all documents and used directly in the tool handler.
    async getDocumentById(id: string): Promise<GranolaDocument | null> {
      const allDocs = await this.getAllDocuments();
      return allDocs.find((doc) => doc.id === id) || null;
    }
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 a transcript but doesn't mention any behavioral traits like error handling (e.g., what happens if the ID is invalid), authentication needs, rate limits, or response format. This leaves significant gaps for a tool with no annotation support.

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 that efficiently conveys the core action without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

Given the complexity of a retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what a 'Granola transcript' entails, the expected return values, or any behavioral context. This leaves the agent with insufficient information to use the tool effectively beyond the basic parameter.

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 schema description coverage is 100%, with the 'id' parameter fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('a specific Granola transcript'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'search_granola_transcripts' or 'get_granola_document', which could retrieve similar resources. This prevents a perfect 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. For example, it doesn't specify that this is for retrieving a single transcript by ID, while 'search_granola_transcripts' might be for broader queries. Without such context, the agent lacks clear usage instructions.

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/btn0s/granola-mcp'

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