Smart Calendars AI

Create and activate a subscription calendar from structured events. Extract the schedule yourself first. Free within feed allowances. No automatic monitoring is enrolled. Reuse request_id on retries. publication.status reports calendar-file preparation, not subscription access. Check distribution_ready for access at the reported revision; use get_feed_status for current availability. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring, scheduled PDF checks or document refreshes. For requests solely for those unsupported actions, explain the limitation without reading feeds or substituting an edit. For unsupported mailbox requests, offer to work with schedule content the user chooses to provide instead. General ICS explanations need no account access. When sharing a feed or filtered_subscription with distribution_ready=true, offer "Open in calendar app" using that object’s HTTPS subscription_open_url (it redirects to webcal), and "Calendar options" using its subscription_options_url for Apple/default, Google, Outlook and copy-link choices. Retain subscription_url as a copyable HTTPS fallback. Prefer these HTTPS handoff links over putting subscription_webcal_url directly in chat, because some clients do not preserve clickable webcal links. If a handoff URL is absent, use the HTTPS subscription_url and dashboard subscription controls instead. Offer "View or edit" using the feed’s manage_url. For a filtered selection use the nested filtered_subscription links, not the unfiltered feed links. Use the returned URLs exactly; never invent or rewrite their host, path or token. Opening a link does not confirm a subscription; the user must confirm in their calendar app. Do not present inactive or unpublished feeds as ready to subscribe.

List the connected account’s feeds, management links and shared active-feed allowance. Only feeds marked counts_towards_active_limit use a slot; this page’s length is not the account’s usage. Deactivating a counted feed frees a slot but interrupts its subscription access, so ask the user first. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring, scheduled PDF checks or document refreshes. For requests solely for those unsupported actions, explain the limitation without reading feeds or substituting an edit. For unsupported mailbox requests, offer to work with schedule content the user chooses to provide instead. General ICS explanations need no account access. When sharing a feed or filtered_subscription with distribution_ready=true, offer "Open in calendar app" using that object’s HTTPS subscription_open_url (it redirects to webcal), and "Calendar options" using its subscription_options_url for Apple/default, Google, Outlook and copy-link choices. Retain subscription_url as a copyable HTTPS fallback. Prefer these HTTPS handoff links over putting subscription_webcal_url directly in chat, because some clients do not preserve clickable webcal links. If a handoff URL is absent, use the HTTPS subscription_url and dashboard subscription controls instead. Offer "View or edit" using the feed’s manage_url. For a filtered selection use the nested filtered_subscription links, not the unfiltered feed links. Use the returned URLs exactly; never invent or rewrite their host, path or token. Opening a link does not confirm a subscription; the user must confirm in their calendar app. Do not present inactive or unpublished feeds as ready to subscribe.

Read events and the internal revision before editing. Request include_facets first and select returned values for known labels. Facet results describe the entire published active feed, independent of read filters or pagination. Nonempty filters also return filtered_subscription with canonical filters, matching_event_count and unmatched_filter_values. Use its URLs for that selection; top-level subscription URLs remain unfiltered. Event IDs, external keys, dates, removal state and pagination narrow only the read, never the subscription. Filtering changes no events and creates no cloned feed. Before proposing cancellations from a revised PDF/document, read every page of the unfiltered feed; never infer deletion from omitted events. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring, scheduled PDF checks or document refreshes. For requests solely for those unsupported actions, explain the limitation without reading feeds or substituting an edit. For unsupported mailbox requests, offer to work with schedule content the user chooses to provide instead. General ICS explanations need no account access. When sharing a feed or filtered_subscription with distribution_ready=true, offer "Open in calendar app" using that object’s HTTPS subscription_open_url (it redirects to webcal), and "Calendar options" using its subscription_options_url for Apple/default, Google, Outlook and copy-link choices. Retain subscription_url as a copyable HTTPS fallback. Prefer these HTTPS handoff links over putting subscription_webcal_url directly in chat, because some clients do not preserve clickable webcal links. If a handoff URL is absent, use the HTTPS subscription_url and dashboard subscription controls instead. Offer "View or edit" using the feed’s manage_url. For a filtered selection use the nested filtered_subscription links, not the unfiltered feed links. Use the returned URLs exactly; never invent or rewrite their host, path or token. Ope

Read the feed’s last update, subscription availability (distribution_ready), editing access and configured monitoring status. This does not refresh or charge. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring, scheduled PDF checks or document refreshes. For requests solely for those unsupported actions, explain the limitation without reading feeds or substituting an edit. For unsupported mailbox requests, offer to work with schedule content the user chooses to provide instead. General ICS explanations need no account access. When sharing a feed or filtered_subscription with distribution_ready=true, offer "Open in calendar app" using that object’s HTTPS subscription_open_url (it redirects to webcal), and "Calendar options" using its subscription_options_url for Apple/default, Google, Outlook and copy-link choices. Retain subscription_url as a copyable HTTPS fallback. Prefer these HTTPS handoff links over putting subscription_webcal_url directly in chat, because some clients do not preserve clickable webcal links. If a handoff URL is absent, use the HTTPS subscription_url and dashboard subscription controls instead. Offer "View or edit" using the feed’s manage_url. For a filtered selection use the nested filtered_subscription links, not the unfiltered feed links. Use the returned URLs exactly; never invent or rewrite their host, path or token. Opening a link does not confirm a subscription; the user must confirm in their calendar app. Do not present inactive or unpublished feeds as ready to subscribe.

Save one revision to one existing calendar feed owned by the connected account. Submit one fixed-schema change set with up to 250 event changes and/or a feed title or description change; all stored calendar changes commit together in one transaction, or none are saved. The input schema declares every supported change: add creates an event; update changes selected fields or uses reset_fields to restore saved field baselines; delete marks an existing event canceled without permanently erasing it; restore reinstates that same event and may update selected fields; feed_patch changes only the calendar title or description. No dynamic operation discovery, fetched schemas, arbitrary commands or arbitrary endpoints are supported. First use dry_run=true to validate and preview the change set without saving, advancing the revision or spending credits. Show the returned before/after changes and any billing quote, not an invented summary. Obtain approval for a proposed schedule revision before saving it with dry_run=false. Save with the returned preview_receipt and the identical feed_id, expected_revision, request_id, operations and feed_patch. The receipt binds that validated preview, not user consent. Changed proposals or expired previews require a new preview and approval; revision conflicts require reading the feed again before preparing a new preview. Preserve omitted events/fields. For revised PDFs/documents, read the complete unfiltered feed before cancellations, preserve unrelated events and manual fields, and ask when an event match is uncertain. Update matched event IDs; a duplicate add is not an update. Use set with null to clear nullable fields; reset_fields restores saved baselines, not empty values. Use the last read expected_revision to prevent overwriting concurrent changes. On uncertain save retry the identical request_id and payload, including the original preview_receipt, never a new one. Subscribers save without billing prompts. If billing requires one credi

Deactivate a feed without deleting events or resetting editing windows. Confirm the user wants to interrupt subscription access. publication.status reports calendar-file preparation, not subscription access. Check distribution_ready for access at the reported revision; use get_feed_status for current availability. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring, scheduled PDF checks or document refreshes. For requests solely for those unsupported actions, explain the limitation without reading feeds or substituting an edit. For unsupported mailbox requests, offer to work with schedule content the user chooses to provide instead. General ICS explanations need no account access. When sharing a feed or filtered_subscription with distribution_ready=true, offer "Open in calendar app" using that object’s HTTPS subscription_open_url (it redirects to webcal), and "Calendar options" using its subscription_options_url for Apple/default, Google, Outlook and copy-link choices. Retain subscription_url as a copyable HTTPS fallback. Prefer these HTTPS handoff links over putting subscription_webcal_url directly in chat, because some clients do not preserve clickable webcal links. If a handoff URL is absent, use the HTTPS subscription_url and dashboard subscription controls instead. Offer "View or edit" using the feed’s manage_url. For a filtered selection use the nested filtered_subscription links, not the unfiltered feed links. Use the returned URLs exactly; never invent or rewrite their host, path or token. Opening a link does not confirm a subscription; the user must confirm in their calendar app. Do not present inactive or unpublished feeds as ready to subscribe.

Reactivate an existing feed free within account allowances. Does not reset the original editing window or modify events. publication.status reports calendar-file preparation, not subscription access. Check distribution_ready for access at the reported revision; use get_feed_status for current availability. These tools manage Smart Calendars feeds only; they cannot access mailboxes or start source monitoring, scheduled PDF checks or document refreshes. For requests solely for those unsupported actions, explain the limitation without reading feeds or substituting an edit. For unsupported mailbox requests, offer to work with schedule content the user chooses to provide instead. General ICS explanations need no account access. When sharing a feed or filtered_subscription with distribution_ready=true, offer "Open in calendar app" using that object’s HTTPS subscription_open_url (it redirects to webcal), and "Calendar options" using its subscription_options_url for Apple/default, Google, Outlook and copy-link choices. Retain subscription_url as a copyable HTTPS fallback. Prefer these HTTPS handoff links over putting subscription_webcal_url directly in chat, because some clients do not preserve clickable webcal links. If a handoff URL is absent, use the HTTPS subscription_url and dashboard subscription controls instead. Offer "View or edit" using the feed’s manage_url. For a filtered selection use the nested filtered_subscription links, not the unfiltered feed links. Use the returned URLs exactly; never invent or rewrite their host, path or token. Opening a link does not confirm a subscription; the user must confirm in their calendar app. Do not present inactive or unpublished feeds as ready to subscribe.