Skip to main content
Glama
Sign In
Penpot MCP Server

Penpot MCP Server

by zcube
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_comment

Delete a comment from a Penpot design by providing its comment ID. Optionally include a share ID to remove comments from a shared project.

Instructions

Delete a comment

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": {
      "commentId": "<commentId>"
    },
    "name": "delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
shareIdNoShare ID (optional)
commentIdYesComment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action, failing to mention that deletion is permanent, whether permissions are required, or what happens to associated data such as replies. This is a significant gap for an irreversible mutation.

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 a single short sentence with no unnecessary words. It is front-loaded and every word contributes to the meaning.

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?

Despite the simple tool and complete parameter schema, the lack of annotations and output schema leaves the description without important context. It does not explain the destructive nature, potential side effects, or expected response, making it incomplete for reliable invocation.

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 input schema provides descriptions for both parameters (shareId and commentId), achieving 100% coverage. The description adds no additional meaning beyond what the schema already contains, so the baseline score of 3 applies.

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 'Delete a comment' uses a specific verb and resource, clearly distinguishing it from sibling tools like delete_comment_thread and update_comment. Even without a title, the purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, conditions for use, or scenarios where this tool is preferred over other comment-related operations. The description simply restates the action.

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