Skip to main content
Glama
Sign In
Penpot MCP Server

Penpot MCP Server

by zcube
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_comment_thread

Add a comment thread to a specific frame in a Penpot design page, enabling team feedback and collaboration.

Instructions

Create a new comment thread on a page

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": {
      "fileId": "<fileId>",
      "pageId": "<pageId>",
      "frameId": "<frameId>",
      "content": "<content>"
    },
    "name": "create_comment_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoX position
yNoY position
fileIdYesFile ID
pageIdYesPage ID
contentYesComment content (max 750 chars)
frameIdYesFrame ID where comment is placed
shareIdNoShare ID (optional)
mentionsNoUser IDs to mention

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?

No annotations provided; description only states the action, no side effects, permissions, return format, or behavior. Minimal for a write operation.

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?

Single sentence, front-loaded, zero waste.

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 complete schema, the description lacks context for a creation tool with 8 parameters—no return info, no prerequisites, no clarification on thread/comment relationship.

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 covers 100% of parameters, so baseline 3; description adds no param-specific meaning beyond the schema.

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?

Clear verb+resource: 'Create a new comment thread on a page' – specific and distinguishes from 'create_comment' and 'list_comment_threads'.

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 on when to use this vs create_comment or update_comment_thread_position; no alternatives or exclusions.

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