Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Report Flagged Content

report_flagged_content
Destructive

Submit a report for flagged posts, comments, or messages that violate community guidelines to Circle moderators. Requires confirmation to change community state.

Instructions

Report Flagged Content. Changes community state and requires confirm=true for the user-requested action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
flagged_contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "flagged_content": {
+    "properties": {
+      "content_id": {
+        "type": "integer"
+      },
+      "content_type": {
+        "enum": [
+          "post",
+          "comment",
+          "connect/connection",
+          "chat_room_message"
+        ],
+        "type": "string"
+      },
+      "reported_reason_body": {
+        "type": "string"
+      },
+      "reported_reason_type": {
+        "enum": [
+          "harassment",
+          "spam",
+          "incorrect_location",
+          "against_guidelines",
+          "other"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "content_id",
+      "content_type",
+      "reported_reason_type",
+      "reported_reason_body"
+    ],
+    "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 / flagged_content / $ref
      Added value: +"#/$defs/flagged_content"
    • removedInput schema / properties / flagged_content / properties
      Removed value: -{
-  "content_id": {
-    "type": "integer"
-  },
-  "content_type": {
-    "enum": [
-      "post",
-      "comment",
-      "connect/connection",
-      "chat_room_message"
-    ],
-    "type": "string"
-  },
-  "reported_reason_body": {
-    "type": "string"
-  },
-  "reported_reason_type": {
-    "enum": [
-      "harassment",
-      "spam",
-      "incorrect_location",
-      "against_guidelines",
-      "other"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / flagged_content / required
      Removed value: -[
-  "content_id",
-  "content_type",
-  "reported_reason_type",
-  "reported_reason_body"
-]
    • removedInput schema / properties / flagged_content / type
      Removed value: -"object"
    • addedInput schema / properties / payload / properties / flagged_content / $ref
      Added value: +"#/$defs/flagged_content"
    • removedInput schema / properties / payload / properties / flagged_content / properties
      Removed value: -{
-  "content_id": {
-    "type": "integer"
-  },
-  "content_type": {
-    "enum": [
-      "post",
-      "comment",
-      "connect/connection",
-      "chat_room_message"
-    ],
-    "type": "string"
-  },
-  "reported_reason_body": {
-    "type": "string"
-  },
-  "reported_reason_type": {
-    "enum": [
-      "harassment",
-      "spam",
-      "incorrect_location",
-      "against_guidelines",
-      "other"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / payload / properties / flagged_content / required
      Removed value: -[
-  "content_id",
-  "content_type",
-  "reported_reason_type",
-  "reported_reason_body"
-]
    • removedInput schema / properties / payload / properties / flagged_content / type
      Removed value: -"object"
  2. 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 declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is largely covered. The description adds that this changes community state and requires confirm=true for the user-requested action, which is useful but overlaps the schema's confirm documentation. It omits what gets changed, permission requirements, and side effects.

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?

Two sentences is compact, but the first is pure title repetition and earns nothing, while the second crams the only real information (state change + confirm) into one line. Front-loading is weak because the substantive clause comes second.

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 a nested flagged_content object and three mutually exclusive body mechanisms (payload, payload_file, body flags), the description explains none of them and has no output schema to fall back on. An agent cannot tell what the call returns or which body form to choose.

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 high (80%), so the schema already documents account, confirm, payload and payload_file. The description only echoes confirm=true and adds no syntax or semantics beyond the structured fields. Baseline 3 applies when the schema carries the burden.

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 merely restates the tool name and title verbatim ('Report Flagged Content'), adding no verb+resource detail beyond the identifier. It never explains what reporting actually does to the flagged content or how it differs from the sibling list_flagged_content. The second sentence describes behavior, not purpose.

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 or when-not-to-use guidance, and no mention of the obvious alternative list_flagged_content. The only usage-flavored statement is about confirm=true, which is already documented in the schema rather than being routing guidance.

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