Skip to main content
Glama

Deactivate a calendar

deactivate_feed
DestructiveIdempotent

Deactivates a feed for an explicit user request to interrupt its subscription access, without deleting events or resetting editing windows. User approval of that access interruption is required. A counted active feed releases its allowance slot. publication.status reports calendar-file preparation, not subscription access. distribution_ready reports subscription availability at the returned revision; availability may change afterward. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feed_id": "<feed_id>",
      "expected_revision": "<expected_revision>",
      "request_id": "<request_id>"
    },
    "name": "deactivate_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
feed_idYesIdentity of the selected calendar, as returned in feed results.
request_idYesOpaque, non-personal idempotency key for this operation. Identical retries retain the same key and payload to prevent duplicate changes. User identifiers, chat/session IDs, telemetry and personal data are outside this field’s scope.
expected_revisionYesLast read feed revision; prevents overwriting concurrent edits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / feed_id / description
      Previous value: -"Feed identity returned by a previous feed tool; used to address the selected calendar only."New value: +"Identity of the selected calendar, as returned in feed results."
    • changedInput schema / properties / request_id / description
      Previous value: -"Generate an opaque key for this save and reuse it unchanged for retries, to prevent duplicate changes. Not a user identifier, chat/session ID, or telemetry. Do not include personal data."New value: +"Opaque, non-personal idempotency key for this operation. Identical retries retain the same key and payload to prevent duplicate changes. User identifiers, chat/session IDs, telemetry and personal data are outside this field’s scope."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Adds real context beyond the annotations: events are not deleted, editing windows are untouched, a counted active feed releases an allowance slot, and distribution_ready/publication.status semantics govern access. Some of this (mailbox access, PDF checks, source monitoring disclaimers) is irrelevant to this tool and dilutes the useful disclosure.

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

Conciseness2/5

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

The critical scoping sentence is front-loaded, but the body sprawls into unrelated platform boilerplate about mailbox access, source-document retrieval, scheduled PDF checks and document refresh, plus a long glossary of four URL fields. Much of this does not earn its place in a deactivation tool.

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?

For a destructive, idempotent mutation with no output schema, the description does cover what is affected and what is preserved, plus how the returned subscription links behave. The irrelevant denial clauses are noise rather than gaps.

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 description coverage is 100%, so feed_id, expected_revision and request_id are already fully documented in the schema. The description contributes nothing about any of the three parameters, so the baseline 3 applies.

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?

Opens with a specific verb+resource ('Deactivates a feed') and immediately scopes the effect ('interrupt its subscription access, without deleting events or resetting editing windows'), which separates it from a delete operation. It does not explicitly contrast with reactivate_feed, so the sibling differentiation is only implicit.

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

Usage Guidelines4/5

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

States the triggering condition ('explicit user request') and a prerequisite ('User approval of that access interruption is required'), which is usable guidance. It never names reactivate_feed or explains when to prefer reactivation over deactivation, so alternatives are left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources