Calendar tools should expose recurring series master IDs and support whole-series updates

Summary

WorkIQ calendar tools can update individual calendar event occurrences, and series-level updates appear to work if the caller already has the recurring series master event ID. However, the normal calendar read/list tool responses do not expose enough recurrence metadata to safely discover or target the series master.

This makes recurring calendar cleanup difficult and error-prone.

Scenario

A user wants to clean up recurring calendar series such as office hours, learning meetings, or FYI meetings by applying a category and setting free/busy consistently across the whole series.

Desired operation:

• Set category on the full recurring series
• Set showAs on the full recurring series
• Optionally support “this and future” semantics

What works today

If the caller obtains the series master event ID through another path, UpdateEvent can update the series master successfully.

For example, Outlook Web’s “View series” page URL contains an encoded series master ID. Passing that encoded ID to UpdateEvent successfully updates the series-level category/free-busy state, and future occurrences reflect the update.

What is missing

WorkIQ calendar reads for recurring event occurrences do not expose fields such as:

• type
• seriesMasterId
• iCalUId
• recurrence
• webLink

Even when these fields are requested via select options, the tool response is normalized and omits them.

As a result, an assistant can see occurrence IDs but cannot reliably identify the series master without scraping Outlook Web UI state or using another non-WorkIQ path.

Requested capability

Please add one or both of the following:

1. Expose recurrence metadata in calendar read/list/get responses:

   • type
   • seriesMasterId
   • iCalUId
   • recurrence
   • webLink

2. Add first-class recurring-series operations:

   • update entire series
   • update this-and-future occurrences
   • set categories on a series
   • set showAs on a series
   • accept/decline/follow an entire series

Why this matters

Updating occurrence-by-occurrence is slow, throttling-prone, and confusing in Outlook because some future instances may remain unchanged. For calendar hygiene workflows, assistants need a safe, first-class way to distinguish:

• one-off event
• recurring occurrence
• recurring series master

and then apply the user’s intent at the correct scope.

Related but different

There are existing issues about adding category support to calendar updates. This request is specifically about recurrence metadata and series-scoped updates. Category writes are useful, but without series discovery they still require per-occurrence updates or an external workaround.

Start by tracing the calendar read/list/get response normalization and the UpdateEvent handling described in the issue. Determine how recurrence metadata can be preserved and which series scopes the tools can support. Done means callers can distinguish one-off events, recurring occurrences, and series masters, then safely apply the requested series-level updates.