Skip to main content

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
Key Features:
  • 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)
Advantages:
  • 4-6x fewer tokens than full transcripts
  • Quick access to key points
  • Efficient when comparing multiple meetings

Parameters

ParameterTypeRequiredDescription
noteGuidstringYesUnique note identifier
summaryIdnumberOptionalSpecific summary ID to retrieve. If omitted, returns the first (default) summary.
formatenumOptionalOutput format: "MARKDOWN" (default) or "PLAIN_TEXT"

noteGuid (required)

The unique identifier of the note to retrieve. Example:
{
  "noteGuid": "abc-123-def"
}
How to Get Note GUID:
  1. Use search_notes to find meetings
  2. Use the noteGuid from 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.
Discovering Available SummariesUse the list_note_summaries tool to see all summaries available for a given note, including their IDs and template names.
Example:
{
  "noteGuid": "abc-123-def",
  "summaryId": 42
}

format (optional)

The output format for the summary content. Defaults to "MARKDOWN".
ValueDescription
"MARKDOWN"Returns content with Markdown formatting (headings, lists, bold, etc.)
"PLAIN_TEXT"Returns content as plain text without formatting
Example:
{
  "noteGuid": "abc-123-def",
  "format": "PLAIN_TEXT"
}

Response Format

Success Response

{
  "noteGuid": "abc-123-def",
  "summaryId": 42,
  "template": "meeting-summary",
  "content": "## Meeting Summary\n...",
  "format": "MARKDOWN",
  "createdAt": "2024-01-15T11:00:00Z"
}
Field Descriptions:
FieldTypeDescription
noteGuidstringUnique note identifier
summaryIdnumberID of this summary
templatestringTemplate name used to generate the summary
contentstringAI-generated meeting summary content
formatstringFormat of the content ("MARKDOWN" or "PLAIN_TEXT")
createdAtstringWhen the summary was generated (ISO 8601)

Usage Examples

Example 1: Basic Usage

AI Request:
Show me the summary of note abc-123-def
MCP Call:
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "get_note_summary",
    "arguments": {
      "noteGuid": "abc-123-def"
    }
  },
  "id": 1
}
Response:
{
  "jsonrpc": "2.0",
  "result": {
    "noteGuid": "abc-123-def",
    "summaryId": 42,
    "template": "meeting-summary",
    "content": "## Q4 Marketing Strategy Meeting\n\n**Key Decisions:**\n- 20% revenue increase target\n- $50,000 marketing budget approved\n\n**Core Discussion:**\n- 30% website traffic increase\n- New customer acquisition strategy\n\n**Action Items:**\n- John: Marketing plan draft (11/20)",
    "format": "MARKDOWN",
    "createdAt": "2025-11-10T11:00:00Z"
  },
  "id": 1
}

Example 2: Request Plain Text Format

MCP Call:
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "get_note_summary",
    "arguments": {
      "noteGuid": "abc-123-def",
      "format": "PLAIN_TEXT"
    }
  },
  "id": 1
}

Example 3: Combined with search_notes

AI Request:
Show me summaries of recent marketing meetings
Workflow:
1. search_notes(content: "marketing", createdAt: "recent")
   -> Found noteGuid "abc-123-def"

2. get_note_summary(noteGuid: "abc-123-def")
   -> Retrieved summary

Example 4: Comparing Multiple Meetings

AI Request:
Summarize all team meetings from this week
Workflow:
1. search_notes(createdAt: "this week", content: "team meeting")
   -> Found 3 meetings (abc-123, def-456, ghi-789)

2. get_note_summary(noteGuid: "abc-123")
3. get_note_summary(noteGuid: "def-456")
4. get_note_summary(noteGuid: "ghi-789")

5. Compare and analyze all 3 summaries
AI Response:
This Week's Team Meetings:

Meeting 1 (11/8): Weekly Sprint Review
- Completed: 5 tasks
- In Progress: 3 tasks
- Issues: Server performance problems

Meeting 2 (11/10): Q4 Goals Check-in
- Achievement rate: 75%
- Need additional resources
- Timeline adjustments required

Meeting 3 (11/12): Product Roadmap
- Finalized priority for 3 new features
- December release target
- Design review scheduled

When to Use

Quick Overview Needed
  • Only need meeting highlights
  • Full transcript not necessary
Comparing Multiple Meetings
  • Weekly meeting summaries
  • Project progress tracking
Efficient Information Gathering
  • Token savings important
  • Fast response required
Decision Making
  • Deciding which meetings to review in detail
  • Assessing meeting importance
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 LengthAverage ResponseMaximum Response
30 minutes0.5 seconds2 seconds
1 hour1 second3 seconds
2 hours1.5 seconds5 seconds

Token Usage

Meeting LengthSummary TokensTranscript TokensSavings
30 minutes~200-400~1,500-2,50085%
1 hour~300-600~3,000-5,00088%
2 hours~500-800~6,000-10,00090%
Token EfficiencySummaries use 80-90% fewer tokens than full transcripts. Always start with summaries before loading complete transcripts.

Common Errors

Missing Note GUID

Solution: Provide the noteGuid parameter.

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 GUID using search_notes.

Summary Not Found

Possible Causes:
  • The specified summaryId does not exist for this note
  • The note has no summaries generated yet
Solution: Use list_note_summaries to check available summaries for the note.