Skip to main content
Glama

list_meetings

Retrieve recorded meetings newest first with IDs, titles, dates, durations, and optional summaries; filter by title substring or date range.

Instructions

List recorded meetings, newest first. Returns id, title, date, and duration for each; include "summary" adds each meeting's summary, so one call covers several meetings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum meetings to return (default 20; with summaries default 10, at most 50).
queryNoCase-insensitive title substring filter.
sinceNoOnly meetings on or after this local calendar day (YYYY-MM-DD).
untilNoOnly meetings on or before this local calendar day (YYYY-MM-DD).
includeNo"summary" adds each meeting's summary. The summaries share 20000 characters; a cut one has summary_truncated, and get_meeting reads it whole.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. It usefully discloses ordering (newest first) and the exact return fields, but does not state read-only behavior, permission requirements, what happens when no meetings match, or how pagination works beyond the schema's limit default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and ordering, followed by return fields and the summary-include tradeoff. Minor density in the second sentence, but no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description appropriately names the return fields (id, title, date, duration). For a read-only list tool with fully documented optional parameters, the main remaining gap is explicit routing versus search_meetings, not the mechanics of calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all five parameters are already documented with defaults and formats. The description adds a useful efficiency note about include="summary" covering several meetings, but most parameter meaning is left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list recorded meetings), plus ordering (newest first) and the returned fields. It does not differentiate from the sibling search_meetings, so an agent must infer that filtering-by-query belongs here rather than there.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'List recorded meetings' and the note that include="summary" covers several meetings in one call, but there is no explicit when-to-use guidance, no exclusion of cases better served by search_meetings, and no prerequisites stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.