Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update a community member

update_member
Destructive

Modify a community member's profile, preferences, or spaces. Requires explicit confirmation to change community state.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
avatarNosigned_id of the avatar returned from the direct upload endpoint
accountNoNamed private Circle account; selects credentials, not a remote community ID.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON request body instead of body flags. Supports nested Tiptap, maps and nullable values.
headlineNo
member_idYesID of the community member
space_idsNo
is_flaggedNo
preferencesNo
member_sinceNoEffective "member since" / joined date. Cannot be in the future.
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
member_tag_idsNo
space_group_idsNo
community_member_profile_fieldsNoProfile fields key value pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "preferences": {
+    "properties": {
+      "make_my_email_public": {
+        "type": "boolean"
+      },
+      "messaging_enabled": {
+        "type": "boolean"
+      },
+      "messaging_enabled_by_admin": {
+        "type": "boolean"
+      },
+      "visible_in_member_directory": {
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  }
+}
    • 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 / payload / properties / preferences / $ref
      Added value: +"#/$defs/preferences"
    • removedInput schema / properties / payload / properties / preferences / properties
      Removed value: -{
-  "make_my_email_public": {
-    "type": "boolean"
-  },
-  "messaging_enabled": {
-    "type": "boolean"
-  },
-  "messaging_enabled_by_admin": {
-    "type": "boolean"
-  },
-  "visible_in_member_directory": {
-    "type": "boolean"
-  }
-}
    • removedInput schema / properties / payload / properties / preferences / type
      Removed value: -"object"
    • addedInput schema / properties / preferences / $ref
      Added value: +"#/$defs/preferences"
    • removedInput schema / properties / preferences / properties
      Removed value: -{
-  "make_my_email_public": {
-    "type": "boolean"
-  },
-  "messaging_enabled": {
-    "type": "boolean"
-  },
-  "messaging_enabled_by_admin": {
-    "type": "boolean"
-  },
-  "visible_in_member_directory": {
-    "type": "boolean"
-  }
-}
    • removedInput schema / properties / preferences / type
      Removed value: -"object"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the mutation profile is covered. The description adds one genuinely new behavioral fact - the confirm=true guardrail - but "changes community state" is largely redundant with the destructive annotation and nothing is said about auth, reversibility, or side effects on related resources.

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 verb+resource and the confirm requirement. Efficient, though "Changes community state" carries little weight beyond what the destructive annotation already tells the agent.

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 destructive, non-idempotent mutation with 15 parameters, nested payload, and no output schema, this description is far too thin. It omits which fields are updatable, the payload/payload_file/flag exclusivity rules, and any confirmation semantics beyond a single phrase.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 15 parameters, nested objects, and only 53% schema description coverage, the schema leaves many fields undocumented. The description adds no parameter meaning at all beyond echoing confirm, and says nothing about the mutually exclusive payload / payload_file / body-flag patterns the schema hints at.

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 clear verb (update) and resource (community member), matching the title. However, it does nothing to distinguish this from close siblings like update_community, create_member, remove_member, or ban_community_member, so the agent must infer scope from the name alone.

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?

The sentence "requires confirm=true for the user-requested action" gives one useful precondition for invocation. Beyond that there is no guidance on when to use this versus alternatives, nor which fields are appropriate to update versus the create/delete sibling tools.

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