Penpot MCP Server

Overview Schema Source Related Servers Discussions Admin

delete_comment_thread

Delete a comment thread by providing its ID, removing the entire discussion from the design. Maintain clean and focused Penpot projects.

Instructions

Delete a comment thread

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": {
      "threadId": "<threadId>"
    },
    "name": "delete_comment_thread"
  }
}

Input Schema

Name	Required	Description	Default
`threadId`	Yes	Thread ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only states the action (delete) without mentioning irreversible effects, cascading deletion of comments, permissions required, or any side effects. A delete operation with zero context about consequences is opaque.

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?

The description is a single concise sentence with no fluff, easy to scan. However, it is slightly under-specified; a two-sentence version that adds behavioral context would still be concise and more useful. Still, for a simple tool the size is acceptable.

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?

The tool is a destructive operation with no output schema and no annotations. The description provides no information about return values, error conditions, or what happens to nested comments. Given the minimal context, the description is incomplete for an agent to safely invoke this 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?

The single parameter threadId has a schema description "Thread ID" (100% coverage). The tool description adds no extra meaning about how threadId is used or where it comes from. Per the baseline rule for high schema coverage, a score of 3 is appropriate.

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 description "Delete a comment thread" is essentially a natural-language restatement of the tool name. It provides no additional detail about the scope or effect beyond the name itself, making it tautological. While the resource is clear, it fails to add any distinguishing information relative to the obvious sibling delete_comment.

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 offers no guidance on when to use this tool versus alternatives such as delete_comment or other thread operations. There is no mention of intended use cases, prerequisites, or conditions that would help an agent choose this tool correctly.

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

Deploy Server