Skip to main content
Tiro MCP tools are designed around a Progressive Disclosure pattern — load metadata first, details only when needed. The workflows below show how to chain tools for common tasks while keeping token usage minimal.
New to Tiro MCP? Start with the Overview to understand the architecture, then set up your client before trying these workflows.

​
How to Find a Meeting and Read What Was Discussed

Tiro’s note-discovery surface is a 3-tier progression: start lightweight with list_notes, deepen to search_notes when you need document content, and only reach for get_note_transcript when verbatim spoken words are required. Most user questions stop at tier 1 or tier 2.

​
Step-by-step

1

List candidate notes (cheapest)

Call list_notes with an optional query.keyword and filter to narrow the result. Returns metadata only (~50 tokens per note).
Use filter.folderId to scope to a specific folder, or omit query.keyword entirely to browse a folder by date.
2

Read documents for matched notes

When you need to understand what was discussed (not just see which notes match), call search_notes with a required keyword. The response carries each matched note’s primary documents (one-pager, custom) inline, HTML-stripped and capped at 5KB per document.
Returns up to 10 matched notes with their documents (~1,500 tokens per note). Most queries end here — the curated documents typically capture the team’s decisions and action items.
3

Fetch a single AI summary (optional)

If you need a summary overview, call get_note with include: ["summary"].
Returns key decisions, action items, and highlights (200–800 tokens).
4

Load the full transcript (last resort)

Only when you need exact quotes or specific spoken words, call get_note_transcript. Returns timestamped paragraphs and a markdown-friendly transcription string (~3,000–5,000 tokens per hour of meeting).

​
Token Usage

​
Frequently Asked Questions

Use list_notes when you need to know which notes exist — by folder, by date, or by keyword presence. Returns metadata only.Use search_notes when you need to understand the context behind a topic — its decisions, action items, or conclusions. Returns matched notes with their documents inline. Keyword is required.
Try broader criteria:
  • Drop or shorten the query.keyword.
  • Widen the filter.createdAtFrom / createdAtTo range or remove it.
  • Verify the note is “Completed” in your Tiro Dashboard — incomplete notes are excluded automatically.
Prefer search_notes. Curated documents are typically 10× more compact than the raw transcript and capture the team’s decisions, action items, and conclusions in their intended structure. Use get_note_transcript only when you need verbatim spoken words for a direct quote.
ISO 8601 datetime with timezone: 2026-04-01T00:00:00Z. Date-only formats like 2026-04-01 are not accepted. The range is half-open [from, to).
Yes. Keyword search on list_notes and search_notes works for both user-scoped and workspace-scoped API keys. Omit workspaceGuid to search across all workspaces you can access — a workspace-scoped key automatically searches its own workspace; pass an explicit workspaceGuid (from list_workspaces) to target a specific workspace.

​
How to Generate Structured Documents from Meeting Notes

AI agents can extract action items, decisions, and key takeaways from any meeting using Tiro’s template-based document system. Each document is structured into sections defined by a template.

​
Step-by-step

1

Browse available templates

Call list_document_templates to see what document types are available.
Returns templates like “Meeting Minutes”, “Action Items”, “Decision Log” — each with an id, title, and description.
2

Find the target meeting

Call list_notes to locate the meeting by keyword (or folder, or date range).
3

Retrieve the documents

Call get_note with include: ["documents"] to fetch all generated documents for the note in one call.
Returns all generated documents with their structured sections (e.g., “Decisions”, “Action Items”, “Next Steps”) for the meeting.

​
Frequently Asked Questions

Call list_document_templates first. Each template includes a description field explaining its purpose. Use get_document_template with a specific templateId to see the full section structure before requesting documents.
get_note(include: ["documents"]) returns an empty array. Documents must be generated from the Tiro app first — the MCP server provides read access to existing documents. Ask the note owner to generate the document in Tiro.

​
Tips for AI Agent Developers

​
Token Optimization

  • Always start with list_notes (~50 tokens per note); deepen to search_notes (~1,500 tokens per note) only when document content is needed; reach for get_note_transcript only when verbatim quoting is required.
  • Use pagination.size to bound results: list_notes defaults to 20 (max 100); search_notes defaults to 10 (max 30 — smaller because each result includes documents).
  • Prefer MARKDOWN format on summaries and documents — more structured and easier for LLMs to parse.

​
Error Handling

  • 401 and 403 responses include action_url and docs_url fields — surface these to you for self-service resolution
  • 429 responses include a Retry-After header — respect it before retrying
  • See Troubleshooting for a full error reference

​
Choosing the Right Tool

Browse the full Tool Reference for the complete tool surface.