Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Community Member Charges List

list_charges
Read-onlyIdempotent

Retrieve and filter community member charges by status, currency, platform, date, amount, or member, with bounded paginated reads that count against API quota.

Instructions

Community Member Charges List. Reads community data. Supports bounded all_pages; every page counts against the API quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
sortNoSort field. Defaults to created_at.
queryNoFree-text search
statusNoComma-separated list of statuses (e.g. paid,refunded,partial_refunded)
accountNoNamed private Circle account; selects credentials, not a remote community ID.
currencyNoComma-separated list of currency codes
per_pageNoRecords per page (max 100)
platformNoComma-separated list of platforms (web, app_store, play_store)
all_pagesNoRead bounded page/per_page pages; each request consumes API quota. Not a snapshot or guaranteed complete backup.
directionNoSort direction. Defaults to desc.
max_itemsNoMaximum returned records with all_pages=true, default 1000. At most 100 requests; output includes continuation state.
amount_gteNoMinimum charge amount (in currency subunits)
amount_lteNoMaximum charge amount (in currency subunits)
paywall_idsNoComma-separated list of paywall IDs
member_emailNoFilter by community member email (partial match)
processor_idNoFilter by exact processor (charge) ID
created_at_gteNoOnly include charges created on/after this date (ISO8601)
created_at_lteNoOnly include charges created on/before this date (ISO8601)
paywall_price_typeNoComma-separated list of paywall price types (e.g. subscription,onetime,installments)
community_member_idNoFilter by community member ID
invoice_processor_idNoFilter by exact invoice processor ID
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. First observedv2.0.0

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's contribution is the quota/bounded-read context: 'Supports bounded all_pages; every page counts against the API quota.' That is genuinely useful, but it says nothing about continuation state, max_items interaction, or result shape.

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?

Very short and front-loaded, which is good, but the opening sentence is redundant with the title and therefore does not earn its place. Only the final clause carries unique information.

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 24-parameter list tool with no output schema, the description is far too thin. It omits pagination behavior (page/per_page interplay with all_pages and max_items), the continuation state mentioned only in the schema, and any indication of what the response contains.

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% across all 24 parameters, so the schema fully documents parameter meaning and the baseline is 3. The description only touches all_pages at a high level and adds no syntax, defaults, or field semantics beyond what the schema already states.

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

Purpose2/5

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

The first sentence is effectively a restatement of the tool title/name ('list_charges' -> 'Community Member Charges List'), and 'Reads community data' is a vague verb that doesn't specify it enumerates charge records. It does not differentiate this tool from closely related siblings such as export_community_member_charges or list_subscriptions.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, even though the sibling set contains an obvious near-duplicate (export_community_member_charges). The all_pages sentence describes behavior, not selection criteria, so an agent gets no routing help.

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