drop2run-mcp

Official

by Drop-to-run

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Reopen a comment thread

reopen_comment

Idempotent

Reopen a resolved comment thread as its owner, using the site and thread ID to restart discussion on a published page or document.

Instructions

Opens a resolved comment thread on a site again, as its owner.

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": {
      "site": "<site>",
      "thread": "<thread>"
    },
    "name": "reopen_comment"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	Subdomain or site id, from list_sites.
`thread`	Yes	Identifier of the thread, from list_comments.

Output Schema

Name	Required	Description
`id`	Yes	Identifier of the thread, which reply_comment and resolve_comment take.
`url`	Yes	Opens the page at the thread.
`path`	Yes	The page it is on, or the document's path in a documents site.
`quote`	Yes	The words the commenter selected, or the text near a pin; use it to find the source.
`comments`	Yes
`outdated`	Yes	True when it was opened on an earlier version; the words it points at may have changed.
`resolved`	Yes	Whether it is resolved.
`selector`	Yes	The CSS selector of the element it is on.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.5Oct 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the mutation and idempotency profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds a genuine constraint beyond them: the action is performed 'as its owner', signalling an ownership/authorization requirement the agent must satisfy.

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?

A single front-loaded sentence with no filler; the actor constraint is placed at the end where it reads naturally.

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?

With an output schema present, return values need not be described, and the annotations cover safety/idempotency. Ownership and precondition are covered; only explicit failure behavior (e.g. reopening a non-resolved thread) is left unstated.

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 100% and both parameters ('site', 'thread') are documented in-schema with their source tools. The description adds no format or syntax detail beyond that, so the baseline 3 applies.

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 (reopen) plus resource (resolved comment thread) and scope (on a site). It implicitly contrasts with the resolve_comment sibling via 'resolved ... again', though it never names the counterpart explicitly.

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 phrase 'opens a resolved comment thread ... again' implies the precondition (thread must already be resolved) but gives no explicit when/when-not guidance and does not name resolve_comment or reply_comment as alternatives.

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