Skip to main content
Glama

List calendars

list_feeds
Read-onlyIdempotent

Lists the connected account’s feeds, management links and shared active-feed allowance for a requested calendar lookup. Only feeds marked counts_towards_active_limit use a slot; this page’s length is not the account’s usage. Reading changes no feeds or subscription access. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum calendars returned on this page, from 1 to 100; defaults to 50.
offsetNoNumber of matching results skipped before this page; defaults to 0. The response next_offset identifies the next page when present.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum calendars returned on this page, from 1 to 100; defaults to 50."
    • addedInput schema / properties / offset / description
      Added value: +"Number of matching results skipped before this page; defaults to 0. The response next_offset identifies the next page when present."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, the description adds substantial behavioral context: reading changes no feeds or subscription access, only feeds with counts_towards_active_limit use a slot, subscription access requires distribution_ready=true, and opening a link does not confirm a subscription. It also explains the distinct roles of subscription_open_url, subscription_options_url, subscription_url, and manage_url.

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 description is front-loaded with the core listing purpose and then moves through scope, behavioral caveats, and result-link semantics. It is longer than typical, but most sentences add useful context, especially because there is no output schema; the negative capability list is somewhat expansive but still relevant to scope.

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, the description compensates by explaining the returned link types, how they differ, and what subscription access requires. Combined with annotations and full schema coverage for the two parameters, it provides enough context for an agent to invoke the tool correctly without needing to infer key return semantics.

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%, and both limit and offset are fully described in the input schema, so the schema already carries parameter semantics. The description adds a note that page length is not account usage, but it does not otherwise expand on the meaning of the parameters beyond what the schema provides.

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 description states a specific verb and resource: it lists the connected account’s feeds, management links, and active-feed allowance for a calendar lookup. This is distinguishable from sibling tools like get_feed and get_feed_status, which imply singular retrieval and status checks rather than a paginated listing.

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?

The description gives clear context for when this tool applies, including scope limited to the connected account’s Smart Calendars AI feeds and what is not provided. It does not explicitly route the agent to sibling tools such as get_feed, but the listing use case is clear from the text.

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