Skip to main content
Glama
zcube

Penpot MCP Server

by zcube

create_frame

Create a frame container for other shapes with customizable fills, gradients, images, borders, shadows, blur, and blend modes.

Instructions

Create a frame shape (container for other shapes) with colors, gradients, images, borders, shadows, blur, and blend modes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX position
yNoY position
r1NoTop-left corner radius
r2NoTop-right corner radius
r3NoBottom-right corner radius
r4NoBottom-left corner radius
nameNoFrame nameFrame
widthNoWidth
fileIdYesFile ID
heightNoHeight
pageIdYesPage ID
opacityNoOverall frame opacity (0-1)
blendModeNoBlend mode: "normal", "multiply", "screen", "overlay", etc.normal
blurValueNoBlur intensity in pixels (for glassmorphism effect)
fillColorNoBackground color (HEX, e.g., "#FFFFFF")
shadowBlurNoShadow blur radius in pixels
fillImageIdNoImage media ID (from upload_file_media)
fillOpacityNoBackground opacity (0-1)
shadowColorNoShadow color (HEX, e.g., "#000000")#000000
shadowStyleNoShadow style: "drop-shadow" or "inner-shadow"drop-shadow
strokeColorNoBorder color (HEX)
strokeWidthNoBorder width in pixels
borderRadiusNoAll corners radius (shorthand for r1-r4)
gradientEndXNoGradient end X (0-1 normalized)
gradientEndYNoGradient end Y (0-1 normalized)
gradientTypeNoGradient type: "linear" or "radial"
shadowSpreadNoShadow spread in pixels
fillImageNameNoImage name
gradientStopsNoGradient stops as JSON array, e.g., '[{"color":"#667eea","opacity":1,"offset":0},{"color":"#764ba2","opacity":1,"offset":1}]'
shadowOffsetXNoShadow X offset in pixels
shadowOffsetYNoShadow Y offset in pixels
shadowOpacityNoShadow opacity (0-1)
strokeOpacityNoBorder opacity (0-1)
fillImageMtypeNoImage MIME typeimage/png
fillImageWidthNoImage width in pixels
gradientStartXNoGradient start X (0-1 normalized)
gradientStartYNoGradient start Y (0-1 normalized)
fillImageHeightNoImage height in pixels
fillImageKeepAspectRatioNoKeep image aspect ratio
Behavior2/5

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

There are no annotations, so the description carries the full burden. It lists capabilities (colors, gradients, images, etc.) and mentions the container aspect, but does not disclose behaviors such as parameter precedence, validation rules, side effects, or return values. For a create operation, this is a significant gap.

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 sentence that front-loads the core purpose and lists key capabilities without fluff. It is appropriately sized for a tool with many parameters, though the long feature list is slightly dense.

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?

Given the tool's complexity (39 parameters, no output schema), the description is far too brief. It does not provide usage context, return behavior, parameter priorities, or prerequisites beyond what the schema already states. A short feature list is insufficient for such a complex tool.

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%, so the baseline is 3. The description adds a high-level summary of feature categories but does not explain parameter interactions (e.g., how fillColor relates to gradientStops, or required fileId/pageId). It does not meaningfully exceed the schema's own descriptions.

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 clearly states the tool's purpose: 'Create a frame shape (container for other shapes)' with a specific verb and resource. It distinguishes itself from sibling tools like create_rectangle, create_circle, and create_text by emphasizing the frame's role as a container and its rich styling capabilities.

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 description implies when to use this tool (when creating a frame/container or applying complex visual effects) but does not explicitly state alternatives or exclusions. It mentions 'container for other shapes' as a use case but lacks direct guidance on choosing between create_frame and other creation tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zcube/penpot-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server