Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export Community Member Subscriptions

export_community_member_subscriptions
Destructive

Download community member subscription records as CSV with filters for status, dates, platform, paywall, and member details; requires confirm=true.

Instructions

Export Community Member Subscriptions. Changes community state and requires confirm=true for the user-requested action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated list of CSV columns to include
statusNoComma-separated list of statuses (e.g. active,trial,canceled)
accountNoNamed private Circle account; selects credentials, not a remote community ID.
confirmNoSet true only when the user asked for exactly this action.
currencyNoComma-separated list of currency codes
platformNoComma-separated list of platforms (web, app_store, play_store)
timezoneNoTimezone used to render dates in the CSV (defaults to Etc/UTC)
paywall_idsNoComma-separated list of paywall IDs
member_emailNoFilter by community member email (partial match)
start_date_gteNoOnly include subscriptions started on/after this date (ISO8601)
start_date_lteNoOnly include subscriptions started on/before this date (ISO8601)
billing_intervalNoFilter by paywall price billing interval (e.g. month, year)
paywall_price_typeNoComma-separated list of paywall price types (e.g. subscription,onetime,installments)
community_member_idNoFilter by community member ID
scheduled_to_cancelNoFilter by whether the subscription is scheduled to cancel
total_amount_paid_gteNoMinimum total amount paid (in currency subunits)
total_amount_paid_lteNoMaximum total amount paid (in currency subunits)
subscription_processor_idNoFilter by exact subscription processor ID
billing_info_business_nameNoFilter by billing info business name (partial match)
community_member_public_uidNoFilter by community member public UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for the specific user-requested write."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true. The description usefully reconciles the misleading 'Export' name by stating it 'changes community state' and adds the confirm gate as required context, but it never says what is destroyed or altered, nor what the export actually returns.

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?

Two short sentences, front-loaded with the resource and immediately followed by the mutation/confirm constraint. No wasted words, though the second clause is somewhat boilerplate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 20-parameter export tool with no output schema and a near-identical sibling (export_community_member_charges), the description omits output format, whether the export is synchronous, and what state the mutation actually affects. It is too thin given the tool's complexity.

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?

All 20 parameters have full schema descriptions, so the schema already carries the meaning and baseline is 3. The description adds nothing about filters, defaults, or the CSV column semantics beyond what the schema documents.

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?

Names a specific verb (Export) and resource (Community Member Subscriptions), which is enough to separate it from most siblings. However it does not distinguish itself from the closely related export_community_member_charges, and 'Export' suggests a plain read while the tool actually mutates state.

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

Usage Guidelines3/5

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

It states the confirm=true gate is tied to a user-requested action, which is a usable invocation rule. But there is no guidance on when to prefer this over list_subscriptions, export_community_member_charges, or other alternatives.

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

Deploy Server

Other Tools