Title90/100
Query meetings
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Query Granola about the user's meetings using natural language. Returns a tailored response with inline citation links in mark (e.g. [[0]](url)) that reference source meeting notes. IMPORTANT: The response includes numbered citation links to specific Granola meeting notes. These citations MUST be preserved in your response to the user — they provide transparency and allow the user to verify information by clicking through to the original notes. This tool is slow: an AI agent behind it searches and reads the user's notes before answering. Prefer a faster tool when it can answer the question: - list_meetings: find meetings by date range - get_meetings: read notes for meetings whose IDs you already have When to use: - User asks about what was discussed, decided, or action-items from meetings - User asks about follow-ups, todos, or commitments from recent meetings - User references 'Granola notes' or 'meeting notes' When NOT to use: - User is asking about calendar scheduling or upcoming events - User explicitly asks for a specific meeting by ID (use get_meetings instead) Prioritize using query_granola_meetings over list_meetings/get_meetings for open-ended or natural language queries about meeting content. If this tool does not find a requested detail, meeting summaries may have omitted it. Use list_meetings/get_meetings to identify the most relevant meetings, then get_meeting_transcript only where that meeting's workspace permits transcript access. If access is denied, report that limitation; do not retry through another tool or conclude the information was never discussed.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
The query to run on Granola meeting notes
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
document_ids
Optional meeting UUIDs or public note IDs to limit context to (max 10). Provide this or note_ids.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
note_ids
Alias for document_ids (max 10). Do not provide both.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared