commune-mcp

Official

by commune-dev

Overview Schema Source Related Servers Discussions(1)Admin

Python

Remote

untag_thread

Remove specific tags or labels from a thread by providing the thread ID and comma-separated tags to remove.

Instructions

Remove tags/labels from a thread.

Args: thread_id: The thread ID tags: Comma-separated tags to remove (e.g. "urgent,vip")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "thread_id": "<thread_id>",
      "tags": "<tags>"
    },
    "name": "untag_thread"
  }
}

Input Schema

Name	Required	Description	Default
`thread_id`	Yes
`tags`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 28, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations, the description does not disclose behavioral traits such as reversibility, idempotency, permissions, or error behavior. It only states the action and parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with a single purpose sentence and a minimal Args list. No filler words.

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

Completeness4/5

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

While the tool is simple with only two parameters, the description lacks usage guidance and behavioral transparency. However, since an output schema exists, the absence of return documentation is not penalized. The description is adequate but could benefit from context on when to use it.

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

Parameters5/5

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

The schema has 0% description coverage, so the description's Args section is essential. It defines thread_id as 'The thread ID' and tags as 'Comma-separated tags to remove' with an example, adding format and meaning.

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

Purpose5/5

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

The description uses the specific verb 'Remove' with the resource 'tags/labels from a thread', clearly distinguishing it from the sibling 'tag_thread' which adds tags.

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 description provides no guidance on when to use this tool versus alternatives such as tag_thread or assign_thread, nor does it state prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.