Skip to main content
Glama

List recurring meetings

list_recurring_meetings
Read-onlyIdempotent

List recurring meeting series, showing repetition rules and series IDs. Use it to discover regular meetings and get IDs for managing or deleting recurring series.

Instructions

List recurring meeting series — the repetition rules, not the individual meetings.

Use it to answer "what regular meetings do we have" and to find the series id that get_recurring_meeting, the occurrence tools and delete_recurring_meeting need. Series ids are their own id space: a series id is never a meeting id, and the weekly occurrences themselves show up in list_meetings, not here.

Returns the standard list envelope: rows of {id, title, project, start_time, time_zone, frequency, interval, monthly_day, monthly_ordinal, monthly_weekday, end_after, end_date, iterations, duration_hours, location} plus pagination and notes.

Pitfalls. The listing is instance-wide — the endpoint takes no project filter, so scope by reading project on the rows. duration_hours is per occurrence. Recurring meetings are 17.4+ AND a module: where the API predates them, the module is off, or this account may not read meetings, the call still SUCCEEDS with an empty items and the reason in notes — read notes before saying there are no recurring meetings.

Cross-references: get_recurring_meeting(recurring_meeting_id=...) for the schedule with its next occurrences; create_recurring_meeting to start a series; list_meetings for the instantiated occurrences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number.
page_sizeNoSeries per page (max 100).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sumsNoPresent only when show_sums was requested.
itemsNoThe page of results.
notesNoDegradation markers: capped aggregations, unavailable modules, …
groupsNoPresent only when group_by was requested.
paginationYesTotal/page/page_size/has_more.
Behavior5/5

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

The description discloses several behavioral traits beyond annotations: instance-wide listing with no project filter, `duration_hours` per occurrence, and the critical pitfall that the call succeeds with empty items when the API version/module/account cannot read meetings, with the reason in `notes`. This adds substantial value beyond the readOnlyHint and destructiveHint annotations.

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

Conciseness5/5

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

The description is well-structured with clear sections: purpose, usage, return format, pitfalls, and cross-references. Every sentence adds information; there is no fluff. Despite its length, it remains focused and scannable.

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

Completeness5/5

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

Given the tool has an output schema and good annotations, the description covers all necessary context: what it lists, how to use it, return field details, important limitations (instance-wide, version/module caveats), and related tools. Nothing important is missing.

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?

The schema already provides complete descriptions for both `page` and `page_size` (100% coverage), so the baseline is 3. The description adds only a general mention of the 'standard list envelope' but does not elaborate on parameter behavior beyond what the schema states.

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

Purpose5/5

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

The description opens with 'List recurring meeting series — the repetition rules, not the individual meetings,' which states the verb, resource, and exact scope. It explicitly distinguishes from individual meetings and references sibling tools like `list_meetings`, making the purpose unmistakable.

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

Usage Guidelines5/5

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

It directly tells when to use the tool: to answer 'what regular meetings do we have' and to find series IDs needed by other tools. It also explains what it does NOT include (occurrences are in `list_meetings`) and provides cross-references to related tools, giving clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kar-thik/openproject-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server