Skip to main content
Glama

Create a subscription calendar

create_feed
Idempotent

Creates a subscription calendar from user-reviewed structured events and optionally activates it. Intended for an explicit request to save a schedule. The caller supplies the events; source-document extraction and automatic monitoring are not performed. Existing account feed and creation allowances apply. Identical retries retain the original request_id and payload. 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": {
      "request_id": "<request_id>",
      "title": "<title>",
      "events": "<events>"
    },
    "name": "create_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesCalendar title for the reviewed schedule.
eventsYesOne to 250 reviewed schedule entries. Each entry contains event fields and may include a source-stable external_key; the caller supplies this content.
activateNoWhether to activate the new calendar immediately, subject to the account active-feed allowance; defaults to true. False creates a saved inactive preview without subscription access.
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.
descriptionNoA short description of this calendar, not the conversation or user profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / activate / description
      Added value: +"Whether to activate the new calendar immediately, subject to the account active-feed allowance; defaults to true. False creates a saved inactive preview without subscription access."
    • addedInput schema / properties / events / description
      Added value: +"One to 250 reviewed schedule entries. Each entry contains event fields and may include a source-stable external_key; the caller supplies this content."
    • addedInput schema / properties / events / items / properties / event / description
      Added value: +"Structured calendar fields for one event from the reviewed schedule."
    • addedInput schema / properties / events / items / properties / event / properties / end_time / description
      Added value: +"Local event end time in HH:mm format, on end_date when supplied or start_date otherwise. All-day events have no clock time."
    • addedInput schema / properties / events / items / properties / event / properties / is_all_day / description
      Added value: +"True for an all-day calendar event with dates and no clock times; false for a timed event with a local start time and optional end time."
    • addedInput schema / properties / events / items / properties / event / properties / start_date / description
      Added value: +"Event start date in YYYY-MM-DD format, using the event timezone for timed events."
    • addedInput schema / properties / events / items / properties / event / properties / start_time / description
      Added value: +"Local event start time in HH:mm format. All-day events have no clock time."
    • addedInput schema / properties / events / items / properties / event / properties / timezone / description
      Added value: +"IANA timezone for the event local dates and times, for example Europe/Berlin or UTC."
    • addedInput schema / properties / events / items / properties / event / properties / title / description
      Added value: +"Event title from the supplied schedule."
    • addedInput schema / properties / title / description
      Added value: +"Calendar title for the reviewed schedule."
  2. Changed9 schema fields changed
    • changedInput schema / properties / events / items / properties / event / properties / description / description
      Previous value: -"Only event notes the user intends to publish with this calendar. Never send chat history, credentials, health records or unrelated personal context."New value: +"Event notes the user intends to publish with this calendar. Chat history, credentials, health records and unrelated personal context are outside this field’s scope."
    • changedInput schema / properties / events / items / properties / event / properties / end_date / description
      Previous value: -"Inclusive last calendar date, YYYY-MM-DD. Keep a printed multi-day range as one event unless the user asks otherwise."New value: +"Inclusive last calendar date, YYYY-MM-DD. A bounded multi-day range represents one event unless the user requests separate events."
    • changedInput schema / properties / events / items / properties / event / properties / facet_actors / description
      Previous value: -"Source-grounded participants or organizers (people, teams or organizations), not an invented audience such as everyone at a school. Extract from the source in the host. Reuse available facet values or existing tags with consistent spelling and language; do not retag unchanged fields."New value: +"Source-grounded participants or organizers (people, teams or organizations), not an invented audience such as everyone at a school. Source-derived labels use the existing facet vocabulary, spelling and language. Unchanged fields retain their tags."
    • changedInput schema / properties / events / items / properties / event / properties / facet_topic / description
      Previous value: -"Source-grounded stable category, not the full event title. Extract from the source in the host. Reuse available facet values or existing tags with consistent spelling and language; do not retag unchanged fields."New value: +"Source-grounded stable category, not the full event title. Source-derived labels use the existing facet vocabulary, spelling and language. Unchanged fields retain their tags."
    • changedInput schema / properties / events / items / properties / event / properties / facet_venue / description
      Previous value: -"Source-grounded venue name. Extract from the source in the host. Reuse available facet values or existing tags with consistent spelling and language; do not retag unchanged fields."New value: +"Source-grounded venue name. Source-derived labels use the existing facet vocabulary, spelling and language. Unchanged fields retain their tags."
    • changedInput schema / properties / events / items / properties / event / properties / location / description
      Previous value: -"The event venue explicitly supplied in the schedule or requested correction, not the user’s current, home or device location. Do not request or infer user geolocation."New value: +"The event venue explicitly supplied in the schedule or requested correction, not the user’s current, home or device location. User geolocation is outside this field’s scope."
    • addedInput schema / properties / events / items / properties / event / properties / recurrence
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Recurrence configuration, or null for a non-recurring event. An object represents repetition explicitly stated in the source or established by separately listed regular occurrences. A single bounded multi-day range is one occurrence with start_date/end_date. Recurrence objects require all schema fields with valid values; empty or partial objects are invalid.",
      +  "properties": {
      +    "endDate": {
      +      "description": "End date for recurrence in YYYY-MM-DD format, or null if no end date",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "frequency": {
      +      "description": "Base recurrence frequency",
      +      "enum": [
      +        "daily",
      +        "weekly",
      +        "monthly",
      +        "yearly"
      +      ],
      +      "type": "string"
      +    },
      +    "interval": {
      +      "description": "Interval between recurrences (e.g., 2 for every 2 weeks)",
      +      "maximum": 999,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "monthlyType": {
      +      "description": "Type of monthly recurrence: by date or by weekday pattern",
      +      "enum": [
      +        "dayOfMonth",
      +        "dayOfWeek"
      +      ],
      +      "type": "string"
      +    },
      +    "occurrenceCount": {
      +      "description": "Number of occurrences before ending, or null if no occurrence limit",
      +      "minimum": 1,
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "selectedDaysOfMonth": {
      +      "description": "Selected days of month (1-31, -1 for last day, -2 for second-last)",
      +      "items": {
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    },
      +    "selectedMonths": {
      +      "description": "Selected months for yearly recurrence (1-12)",
      +      "items": {
      +        "maximum": 12,
      +        "minimum": 1,
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    },
      +    "selectedWeekdays": {
      +      "description": "Selected weekdays for weekly recurrence",
      +      "items": {
      +        "enum": [
      +          "monday",
      +          "tuesday",
      +          "wednesday",
      +          "thursday",
      +          "friday",
      +          "saturday",
      +          "sunday"
      +        ],
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "weekdayCategory": {
      +      "description": "Category or specific weekday for monthly/yearly patterns",
      +      "enum": [
      +        "day",
      +        "weekday",
      +        "weekend",
      +        "monday",
      +        "tuesday",
      +        "wednesday",
      +        "thursday",
      +        "friday",
      +        "saturday",
      +        "sunday"
      +      ],
      +      "type": "string"
      +    },
      +    "weekdayOrdinal": {
      +      "description": "Ordinal position of weekday in month",
      +      "enum": [
      +        "first",
      +        "second",
      +        "third",
      +        "fourth",
      +        "fifth",
      +        "last",
      +        "secondLast"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "frequency",
      +    "interval",
      +    "selectedWeekdays",
      +    "monthlyType",
      +    "selectedDaysOfMonth",
      +    "weekdayOrdinal",
      +    "weekdayCategory",
      +    "selectedMonths",
      +    "endDate",
      +    "occurrenceCount"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / events / items / properties / external_key / description
      Previous value: -"Source-stable, namespaced event identity, for example school-a:session-104. Do not derive it from a mutable title or date. A duplicate add does not update the event; use its event_id with update."New value: +"Source-stable, namespaced event identity, for example school-a:session-104, retained when a title or date changes. A duplicate add does not update the event; updates address the existing event_id."
    • 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."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare idempotent/readOnly/destructive flags, and the description adds substantial non-redundant context: idempotency semantics via request_id, the distinction between publication.status (file prep) and distribution_ready (subscription access), the fact that opening a link does not confirm a subscription, and account allowance constraints. This is rich transparency beyond the structured fields.

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

Conciseness3/5

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

Purpose is front-loaded, but the description is long and repeats the negative-scope list twice ('source-document extraction and automatic monitoring are not performed' vs. 'No mailbox access, source-document retrieval, automatic source monitoring...'). The URL-link paragraph and repeated constraints inflate length beyond what's strictly needed.

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?

For a 5-parameter, nested-event tool with no output schema, the description compensates well by explaining the returned links (subscription_open_url, subscription_options_url, subscription_url, manage_url), URL non-interchangeability, and the filtered_subscription distinction. An agent has enough to call it and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds meaning by clarifying that the caller supplies events (no extraction), that retries retain the original request_id/payload, and that distribution_ready gates subscription access. It doesn't elaborate on the nested event fields themselves, but it adds genuine semantic context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb (creates), resource (subscription calendar), source (user-reviewed structured events), and optional behavior (activates it). The caller-supplied nature and scope limitation to Smart Calendars AI feeds further sharpen what this tool does, distinguishing it from update-oriented siblings like apply_feed_changes.

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?

'Intended for an explicit request to save a schedule' clearly establishes the triggering condition, and the repeated negations (no source-document extraction, no monitoring) tell the agent what this tool is *not* for. It stops short of naming which sibling to use for updates/deactivation, so it doesn't reach full when/when-not/alternative coverage.

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