Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Community Members

list_members
Read-onlyIdempotent

List community members filtered by active, inactive, or all statuses and member tags. Supports paginated reads to review or export audience data.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
statusNoFilter by member status. Defaults to `active`. - `active`: members who have completed profile setup (`profile_confirmed_at` is set). - `inactive`: invited members who have not yet completed profile setup. This is the same set shown in the admin UI under Audience → Manage → Invited. - `all`: both of the above.
accountNoNamed private Circle account; selects credentials, not a remote community ID.
per_pageNoNumber of records per page
all_pagesNoRead bounded page/per_page pages; each request consumes API quota. Not a snapshot or guaranteed complete backup.
max_itemsNoMaximum returned records with all_pages=true, default 1000. At most 100 requests; output includes continuation state.
member_tag_idsNoFilter by Member Tag IDs (OR logic, comma-separated)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds a genuinely new trait the annotations do not carry: that all_pages is bounded and that every page consumes API quota, which matters for a 7-parameter paginated reader.

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?

Three short sentences, front-loaded with the resource and immediately followed by the quota caveat. No filler, though the terseness leaves real gaps rather than being optimally sized.

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 7-parameter paginated list tool with no output schema and no output description, the definition says nothing about the returned shape, continuation state, or how page/per_page/all_pages/max_items interact in practice. The quota sentence is a start but far short of what an agent needs.

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%, including detailed enum semantics for status, account credential selection, and max_items continuation behavior. The description adds nothing beyond the schema, so the baseline of 3 applies.

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, 'List Community Members,' is a verbatim restatement of the title, and 'Reads community data' adds no specificity. Nothing distinguishes it from the many sibling list/get/search member tools such as search_member, get_member, list_tagged_members, or list_space_members.

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?

There is no when-to-use guidance, no exclusion conditions, and no mention of alternatives like search_member or the access-group/space-scoped member listers. The all_pages/quota note is behavioral caution, not usage routing.

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