Skip to main content
Glama

Reactivate a calendar

reactivate_feed
Idempotent

Reactivates an existing feed for an explicit user request to restore its subscription access, subject to existing account allowances. Does not reset the original editing window or modify events. 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": "reactivate_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

A4.1/5.0
Behavior5/5

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

Beyond annotations, it discloses important side-effect boundaries: it does not reset the editing window or modify events, access depends on distribution_ready, and opening a subscription link does not itself confirm a subscription. It also explains status-field semantics and the limited scope of the connected account’s Smart Calendars AI feeds.

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

Conciseness4/5

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

The purpose is front-loaded in the first sentence, and most subsequent detail is substantive behavioral or result-interpretation context. It is somewhat verbose for a three-parameter operation and would be easier to scan if structured into shorter sections.

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?

With no output schema and a mutation-like operation, the description carries the necessary burden and explains return-link semantics, status fields, subscription confirmation behavior, and scope limits. An agent has enough context to invoke it correctly and interpret the result.

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 all three input parameters are already documented in the schema. The description adds context about revisions and result statuses but does not add meaningfully more detail about feed_id, request_id, or expected_revision.

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?

The description states a specific verb and resource: reactivating an existing feed to restore subscription access. It is clearly distinguishable from read/list/create tools, though it does not explicitly name sibling alternatives such as deactivate_feed.

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?

It gives clear usage context: an explicit user request to restore subscription access, subject to account allowances. It does not state when not to use the tool or explicitly point to a sibling alternative.

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