Why a Calendar MCP Search Can Miss a Shared-Calendar Event

If list_events returns nothing when you search a shared calendar, do not conclude the event is gone. CalendarMCP warns that text search may not work on every non-primary calendar. First repeat the read against that calendar with a bounded time range and no query parameter.

A read-only diagnostic

1. Call list_calendarswith the same API key as the agent. Find the intended calendar's id, account, enabled state, andcanRead grant. A disabled or unreadable calendar is a different problem from an empty search.
2. Call list_events with that exact calendarId,timeMin and timeMax as ISO 8601 timestamps with offsets, and no query. Choose a window around the expected meeting, not the entire calendar history. Start withmaxResults: 100 and expand or page if needed.
3. Compare the returned event's title, start, organizer, and ID with the meeting you meant. Only after finding the right ID should you callget_event or propose an edit. Nothing in this diagnostic creates a test meeting or changes an existing one.

For example, if a search for "handoff" finds nothing on a team calendar, try a no-query read for the week of the handoff on that calendar. This is a hypothetical troubleshooting example, not a report of a customer incident.

What an empty result means

Google's Events: list reference defines q as free-text search over selected fields, including summary, description, location, and attendee or organizer details. It is not an all-fields search. CalendarMCP documents a possible non-primary search limitation, but neither an empty q result nor that warning proves the event exists. A no-query range read is the useful comparison.

The same Google reference says timeMin filters against event end times and timeMax against start times. Include the meeting itself inside your chosen window and supply time-zone offsets. If you are unsure which connected calendar holds it, a no-ID call can fan out over readable calendars; inspect any per-calendar failure warning before treating the response as a complete inventory.

Do not mistake a sample for a full inventory

CalendarMCP defaults maxResults to 10. With an explicitcalendarId, it paginates up to your requested limit and reports a next-page token when more results remain. Without an ID, it queries enabled readable calendars in parallel and truncates the merged result to your limit; that fan-out read is useful for orientation, not an exhaustive search. Narrow the time window and target the calendar by ID if you need to rule out an event. If the no-query read still fails, check the calendar grant and the reported error rather than retrying a write to see what happens.

Product behavior: CalendarMCP tool documentation. API semantics: Google Calendar Events: list, checked October 14, 2026.