Documentation Index
Fetch the complete documentation index at: https://api-docs.tiro.ooo/llms.txt
Use this file to discover all available pages before exploring further.
Overview
get_note_summary returns a condensed summary of the meeting content generated by AI.
Primary Use Cases:
- Quickly understanding meeting highlights
- Comparing multiple meetings
- Reviewing content without loading full transcripts
- Concise summaries (~200-800 tokens)
- Fast response time (0.5-2 seconds)
- Token efficient (80% savings vs. transcripts)
- Multiple output formats (Markdown or plain text)
- 4-6x fewer tokens than full transcripts
- Quick access to key points
- Efficient when comparing multiple meetings
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
noteGuid | string | Yes | Unique note identifier |
summaryId | number | Optional | Specific summary ID to retrieve. If omitted, returns the first (default) summary. |
format | enum | Optional | Output format: "MARKDOWN" (default) or "PLAIN_TEXT" |
noteGuid (required)
The unique identifier of the note to retrieve. Example:- Use
search_notesto find meetings - Use the
noteGuidfrom search results
summaryId (optional)
The ID of a specific summary to retrieve. A single note can have multiple summaries generated from different templates. If omitted, the first available summary is returned. Example:format (optional)
The output format for the summary content. Defaults to"MARKDOWN".
| Value | Description |
|---|---|
"MARKDOWN" | Returns content with Markdown formatting (headings, lists, bold, etc.) |
"PLAIN_TEXT" | Returns content as plain text without formatting |
Response Format
Success Response
| Field | Type | Description |
|---|---|---|
noteGuid | string | Unique note identifier |
summaryId | number | ID of this summary |
template | string | Template name used to generate the summary |
content | string | AI-generated meeting summary content |
format | string | Format of the content ("MARKDOWN" or "PLAIN_TEXT") |
createdAt | string | When the summary was generated (ISO 8601) |
Usage Examples
Example 1: Basic Usage
AI Request:Example 2: Request Plain Text Format
MCP Call:Example 3: Combined with search_notes
AI Request:Example 4: Comparing Multiple Meetings
AI Request:When to Use
Use When
Use When
Quick Overview Needed
- Only need meeting highlights
- Full transcript not necessary
- Weekly meeting summaries
- Project progress tracking
- Token savings important
- Fast response required
- Deciding which meetings to review in detail
- Assessing meeting importance
Don't Use When
Don't Use When
Need Exact Quotes
-> Use
get_note_transcript insteadFinding Specific Statements
-> Use get_note_transcript insteadExtracting Action Items
-> Use get_note_document instead (more structured)Performance
Response Time
| Meeting Length | Average Response | Maximum Response |
|---|---|---|
| 30 minutes | 0.5 seconds | 2 seconds |
| 1 hour | 1 second | 3 seconds |
| 2 hours | 1.5 seconds | 5 seconds |
Token Usage
| Meeting Length | Summary Tokens | Transcript Tokens | Savings |
|---|---|---|---|
| 30 minutes | ~200-400 | ~1,500-2,500 | 85% |
| 1 hour | ~300-600 | ~3,000-5,000 | 88% |
| 2 hours | ~500-800 | ~6,000-10,000 | 90% |
Common Errors
Missing Note GUID
Solution: Provide thenoteGuid parameter.
Note Not Found
Possible Causes:- Note doesn’t exist
- Note has been deleted
- You don’t have access to this note
search_notes.
Summary Not Found
Possible Causes:- The specified
summaryIddoes not exist for this note - The note has no summaries generated yet
list_note_summaries to check available summaries for the note.