Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

reopen_comment_thread

Destructive

Reopen a resolved comment thread by its thread ID to continue discussion or address follow-up issues.

Instructions

Reopen a previously resolved thread.

Free door, tiered answer — Free: On the designs you keep · Pro: ✓ · Business: ✓ · Enterprise: ✓.

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>"
    },
    "name": "reopen_comment_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYesThe thread's id: the ``thread_id`` on any of its comments (a root comment's own ``comment_id``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / thread_id / description
      Added value: +"The thread's id: the ``thread_id`` on any of its comments (a root comment's own ``comment_id``)."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation/risk profile is covered. The description adds plan-gating context (Free/Pro/Business/Enterprise availability) that annotations do not carry, but the 'Free door, tiered answer — Free: On the designs you keep' phrasing is cryptic and never states the actual effect (thread returns to open, commenting resumes) or whether the reopen is reversible.

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?

The first sentence is efficient and front-loaded, but the second sentence is opaque tier marketing ('Free door, tiered answer') that costs space without giving the agent a clear rule. One sentence of real content padded with one sentence of noise.

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 single-parameter mutation with no output schema, the description covers what the tool does and rough plan availability. It omits the concrete post-condition (what state the thread ends in), permission requirements, and error behavior, which matter for a destructive-flagged operation.

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 coverage is 100% and the single parameter's schema description already explains where thread_id comes from (a root comment's comment_id). The description adds nothing beyond the schema, which is the expected baseline for a one-param tool.

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?

States a specific verb and resource ('Reopen a previously resolved thread'), making the inverse of resolve_comment_thread obvious. It does not explicitly name the sibling it undoes, so an agent must infer the pairing from names.

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?

Usage is implied by 'previously resolved thread' — reopen when a resolution needs to be undone. There is no explicit when-to-use, no prerequisites (e.g. required ownership or permissions), and no pointer to resolve_comment_thread or reply_to_comment as alternatives.

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