Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a member filter control

create_filter_control
Destructive

Create a member filter control to add or toggle filters like location, tags, or spaces; confirm=true is required because it changes community state.

Instructions

Create a member filter control. Changes community state and requires confirm=true for the user-requested action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
accountNoNamed private Circle account; selects credentials, not a remote community ID.
confirmNoSet true only when the user asked for exactly this action.
enabledNoWhether to show the filter
payloadNoComplete JSON request body instead of body flags. Supports nested Tiptap, maps and nullable values.
sort_keyNoOptional ordering position; lower values sort first
space_idNoMember space ID; omit for the member directory
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
profile_field_idNoProfile field ID; allowed only when key is profile_field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "key": {
+    "description": "Filter to control; profile_field requires profile_field_id",
+    "enum": [
+      "contact_search",
+      "near_me",
+      "online",
+      "recently_joined",
+      "location",
+      "tags",
+      "profile_field",
+      "spaces",
+      "space_groups",
+      "global"
+    ],
+    "type": "string"
+  }
+}
    • 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."
    • addedInput schema / properties / key / $ref
      Added value: +"#/$defs/key"
    • removedInput schema / properties / key / description
      Removed value: -"Filter to control; profile_field requires profile_field_id"
    • removedInput schema / properties / key / enum
      Removed value: -[
-  "contact_search",
-  "near_me",
-  "online",
-  "recently_joined",
-  "location",
-  "tags",
-  "profile_field",
-  "spaces",
-  "space_groups",
-  "global"
-]
    • removedInput schema / properties / key / type
      Removed value: -"string"
    • addedInput schema / properties / payload / properties / key / $ref
      Added value: +"#/$defs/key"
    • removedInput schema / properties / payload / properties / key / description
      Removed value: -"Filter to control; profile_field requires profile_field_id"
    • removedInput schema / properties / payload / properties / key / enum
      Removed value: -[
-  "contact_search",
-  "near_me",
-  "online",
-  "recently_joined",
-  "location",
-  "tags",
-  "profile_field",
-  "spaces",
-  "space_groups",
-  "global"
-]
    • removedInput schema / properties / payload / properties / key / type
      Removed value: -"string"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotence, so the safety envelope is covered. The description adds real value beyond that by disclosing that the call changes community state and that confirm=true is a hard gate tied to explicit user intent, which is not derivable from the annotations alone.

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, no padding, with the core action front-loaded before the safety constraint. The phrasing 'requires confirm=true for the user-requested action' is slightly circular but compact.

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

Completeness3/5

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

For a 9-parameter mutation tool with a nested payload object and no output schema, the description is thin: it never explains what a filter control is, what happens on success, or how the account/space/global key choices interact. Annotations carry the safety profile and the schema carries parameter detail, so it is minimally viable but leaves conceptual gaps.

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 89%, so the schema already documents all 9 parameters including the payload/body-flag mutual exclusion and the profile_field/profile_field_id dependency. The description adds nothing about parameters beyond restating the confirm requirement, so the baseline 3 is appropriate.

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?

The description states a specific verb ('Create') and resource ('member filter control'), matching the title closely. It does not explicitly distinguish itself from the sibling update_filter_control or delete_filter_control, but 'Create' is unambiguous against them.

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?

The only usage condition given is that confirm=true is required 'for the user-requested action'. There is no guidance on when to create a filter control versus updating an existing one, nor any reference to the sibling tools that would route the agent correctly.

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