Skip to main content

​
Overview

get_note_transcript returns the full conversation transcript (speaker-by-speaker) of a meeting. Primary Use Cases:
  • Understanding complete meeting content
  • Finding specific quotes or statements
  • Analyzing conversation context
  • When exact wording is important
Key Features:
  • Returns complete transcript text
  • Large data size (~3,000-5,000 tokens per hour of meeting)
  • Detailed information (speakers, timestamps)
High Token UsageTranscripts consume significant tokens. Consider using get_note_summary first unless you need verbatim content.

​
Parameters

ParameterTypeRequiredDescription
noteIdnumberYesNote ID (positive integer)

​
noteId (required)

The unique ID of the note to retrieve. Example: 
{
  "noteId": 123
}
How to Get Note ID:
  1. Use search_notes to find meetings
  2. Use the noteId from search results

​
Response Format

​
Success Response

{
  "transcript": "Sarah Kim: Hello everyone, let's start today's meeting.\n\nJohn Park: Thank you. I'll share last week's progress first...\n\nSarah Kim: Great. Shall we discuss the Q4 marketing strategy?\n\n..."
}
Field Descriptions:
FieldTypeDescription
transcriptstringComplete conversation transcript (separated by speaker)
Format: 
{Speaker Name}: {Statement}

{Speaker Name}: {Statement}
...

​
Usage Examples

​
Example 1: Basic Usage

AI Request: 
Show me the full transcript of meeting #123
MCP Call: 
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "get_note_transcript",
    "arguments": {
      "noteId": 123
    }
  },
  "id": 1
}
Response: 
{
  "jsonrpc": "2.0",
  "result": {
    "transcript": "Sarah Kim: Welcome to the Q4 marketing strategy meeting.\n\nJohn Park: Thanks. Let me present our website analytics...\n\n..."
  },
  "id": 1
}

​
Example 2: Progressive Disclosure Pattern

Step 1: Search 
Find recent marketing meetings
Uses search_notes - Fast (~1 second, ~100 tokens) Step 2: Summary 
What was discussed in meeting #123?
Uses get_note_summary - Medium (~2 seconds, ~500 tokens) Step 3: Full Transcript (Only if Needed) 
Show me the exact conversation about budget allocation
Uses get_note_transcript - Slow (~5 seconds, ~4,000 tokens)

​
Token Usage

Typical Meeting (1 hour): ~3,000-5,000 tokens Comparison:
ToolToken UsageWhen to Use
search_notes~50 tokensFinding meetings
get_note_summary~200-800 tokensQuick overview
get_note_transcript~3,000-5,000 tokensNeed exact quotes
get_note_documents~300-2,000 tokensAction items
Token SavingsBefore loading transcripts, try get_note_summary first. It provides key information in 80% fewer tokens.

​
Best Practices

Always follow this order:
  1. search_notes - Find relevant meetings (~50 tokens)
  2. get_note_summary - Review key points (~500 tokens)
  3. get_note_transcript - Only if exact wording needed (~4,000 tokens)
This saves up to 90% of tokens in most cases.
Use full transcripts when you need to:
  • Find exact quotes or statements
  • Analyze detailed conversation flow
  • Understand complete context
  • Reference specific discussions
Don’t use transcripts for:
  • Quick overview (use summary instead)
  • Action items (use get_note_documents)
  • General understanding (use summary)
For very long meetings (2+ hours):
  • Expect 5,000-10,000 tokens
  • May cause timeout (60 seconds)
  • Consider requesting specific sections via summary first
  • Use summary to identify relevant parts before loading full transcript

​
Common Errors

​
Missing Note ID

Solution: Provide the noteId parameter.

​
Invalid Note ID

Solution: Use a positive integer (e.g., 123, not "123" or -1).

​
Note Not Found

Possible Causes:
  • Note doesn’t exist
  • Note has been deleted
  • You don’t have access to this note
Solution: Verify the note ID using search_notes.

​
Request Timeout

Causes:
  • Very long meeting transcript (2+ hours)
  • Server load
Solutions:
  1. Use get_note_summary instead
  2. Retry after a short delay
  3. Contact support if problem persists

​
Performance

Response Time:
Meeting LengthTokensResponse Time
30 minutes~1,500~2 seconds
1 hour~3,000~3 seconds
2 hours~6,000~5 seconds
3+ hours~9,000+~8 seconds (may timeout)
Cache BehaviorTranscripts are cached for 15 minutes. Subsequent requests for the same note will be faster.

​
Next Steps

After retrieving a transcript:

get_note_summary

Get condensed summary for quick reference

get_note_documents

Extract action items and structured data

search_notes

Find other related meetings

Tools Overview

Learn about Progressive Disclosure