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

Tiro provides two tools for working with structured meeting documents:
  • list_note_documents - List all documents generated for a note
  • get_note_document - Retrieve the full content of a specific document
Documents contain structured information extracted from meetings, such as action items, decisions, and section summaries. Each document is generated from a template (e.g., meeting minutes, action items, project brief).
Related ToolsUse list_document_templates to see all available document templates, and get_document_template to inspect a specific template’s structure before requesting documents.

​
list_note_documents

Lists all documents generated for a given note.

​
Parameters

ParameterTypeRequiredDescription
noteGuidstringYesUnique note identifier
templateIdnumberOptionalFilter by template ID to only return documents from a specific template

​
Example Request

List all documents for a note: 
{
  "noteGuid": "abc-123-def"
}
Filter by template: 
{
  "noteGuid": "abc-123-def",
  "templateId": 3
}

​
Response Format

{
  "noteGuid": "abc-123-def",
  "documents": [
    {
      "documentId": 7,
      "template": "meeting-minutes",
      "locale": "ko",
      "createdAt": "2024-01-15T11:30:00Z"
    },
    {
      "documentId": 12,
      "template": "action-items",
      "locale": "en",
      "createdAt": "2024-01-15T11:32:00Z"
    }
  ]
}
Field Descriptions:
FieldTypeDescription
noteGuidstringUnique note identifier
documentsarrayList of documents for this note
documents[].documentIdnumberUnique document ID (use with get_note_document)
documents[].templatestringTemplate name used to generate the document
documents[].localestringLanguage/locale of the document
documents[].createdAtstringWhen the document was generated (ISO 8601)

​
get_note_document

Retrieves the full content of a specific document.

​
Parameters

ParameterTypeRequiredDescription
noteGuidstringYesUnique note identifier
documentIdnumberYesDocument ID (from list_note_documents results)
formatenumOptionalOutput format: "MARKDOWN" (default) or "PLAIN_TEXT"

​
Example Request

Basic usage: 
{
  "noteGuid": "abc-123-def",
  "documentId": 7
}
With plain text format: 
{
  "noteGuid": "abc-123-def",
  "documentId": 7,
  "format": "PLAIN_TEXT"
}

​
Response Format

{
  "noteGuid": "abc-123-def",
  "documentId": 7,
  "template": "meeting-minutes",
  "locale": "ko",
  "sections": [
    {
      "content": "## Action Items\n- ...",
      "format": "MARKDOWN"
    }
  ],
  "createdAt": "2024-01-15T11:30:00Z"
}
Field Descriptions:
FieldTypeDescription
noteGuidstringUnique note identifier
documentIdnumberUnique document ID
templatestringTemplate name used to generate the document
localestringLanguage/locale of the document
sectionsarrayDocument content organized by sections
sections[].contentstringSection content
sections[].formatstringContent format ("MARKDOWN" or "PLAIN_TEXT")
createdAtstringWhen the document was generated (ISO 8601)

​
Usage Examples

​
Example 1: List and Retrieve Documents

Step 1: List available documents MCP Call: 
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "list_note_documents",
    "arguments": {
      "noteGuid": "abc-123-def"
    }
  },
  "id": 1
}
Step 2: Get a specific document MCP Call: 
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "get_note_document",
    "arguments": {
      "noteGuid": "abc-123-def",
      "documentId": 7
    }
  },
  "id": 2
}

​
Example 2: Extract Action Items

AI Request: 
Show me the action items from meeting abc-123-def
Workflow: 
1. list_note_documents(noteGuid: "abc-123-def")
   -> Found documents: meeting-minutes (7), action-items (12)

2. get_note_document(noteGuid: "abc-123-def", documentId: 12)
   -> Retrieved action items document
AI Response: 
Q4 Marketing Strategy Meeting Action Items:

1. John Park
   - Task: Draft marketing plan
   - Due: 2025-11-20

2. Sarah Kim
   - Task: Review budget proposal
   - Due: 2025-11-15

3. Emily Lee
   - Task: Competitor analysis report
   - Due: 2025-11-18

​
Example 3: Weekly Task Compilation

User Request: 
Compile all action items from this week's meetings
AI Workflow: 
1. search_notes(createdAt: "this week")
   -> Found 5 meetings

2. For each meeting:
   list_note_documents(noteGuid: "...")
   -> Find action-items documents

3. get_note_document for each action-items document
   -> Extract and group by assignee

Result:
Sarah Kim:
- Review budget proposal (11/15) - Q4 Marketing Meeting
- Design review (11/18) - Product Meeting
- Team performance report (11/20) - Weekly Sync

John Park:
- Marketing plan draft (11/20) - Q4 Marketing Meeting
- Server performance improvement (11/22) - Tech Meeting
...

​
When to Use

Follow-up Tasks Needed
  • Tracking action items
  • Checking assignee responsibilities
  • Managing deadlines
Structured Information
  • Understanding section content
  • Organizing key decisions
  • Systematic meeting notes
Project Management
  • Extracting tasks
  • Schedule management
  • Team member assignments
Decision Tracking
  • Confirming decisions made
  • Approved budgets/plans
  • Policy changes
Only Need Simple Summary -> Use get_note_summary insteadNeed Full Conversation -> Use get_note_transcript insteadExploration Phase -> Use search_notes instead

​
Performance

​
Response Time

ToolAverage ResponseMaximum Response
list_note_documents0.5 seconds2 seconds
get_note_document1-2 seconds5 seconds

​
Token Usage

Meeting LengthDocument TokensTranscript TokensSavings
30 minutes~300-600~1,500-2,50070%
1 hour~500-1,000~3,000-5,00075%
2 hours~800-1,500~6,000-10,00080%
Structured Data AdvantageDocuments provide structured JSON format, making it easy to extract specific information like action items or decisions without parsing unstructured text.

​
Limitations

​
Current Limitations

AI-Generated DataDocuments are AI-generated with ~85-90% accuracy. For critical information, verify against the full transcript using get_note_transcript.
Known Limitations:
  1. Action Item Recognition
    • Only recognizes explicit task assignments
    • Implicit tasks may be missed
  2. Accuracy Considerations
    • ~85-90% accuracy for AI-generated content
    • Important details should be verified with transcript

​
Common Errors

​
Missing Note GUID

Solution: Provide the noteGuid parameter.

​
Missing Document ID

Solution: Provide the documentId parameter when calling get_note_document. Use list_note_documents to find available document IDs.

​
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.

​
Document Not Found

Possible Causes:
  • The specified documentId does not exist for this note
  • The document has been deleted
Solution: Use list_note_documents to check available documents for the note.

​
No Documents Available

Processing RequiredIf a note has just been created, documents may not be available yet. Wait for processing to complete (usually 1-2 minutes after meeting ends).