Skip to main content
Glama
mahmudcoding

Custom Figma MCP

by mahmudcoding

Create rectangle

figma.create_rectangle

Create a native Figma rectangle with specified position, size, and style properties for automated design editing.

Instructions

Create a native Figma rectangle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
nameNoRectangle
indexNo
styleNo
widthNo
heightNo
pageIdNo
parentIdNo
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'create', without explaining side effects (e.g., whether the rectangle is added to the current page, whether it's selected, or any default styling). This is insufficient for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it lacks structure and essential details. It is under-specified rather than efficiently compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, nested objects, no output schema), the description is severely incomplete. It fails to explain what the rectangle is, how to position it, or what the result looks like. Crucially, it does not mention return values or side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no information about the 9 parameters. With 0% schema coverage, the agent has no guidance on how to set x, y, style, etc. The description is too vague to help with parameter selection.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a native Figma rectangle' states the verb and resource clearly, but does not differentiate it from sibling tools like figma.create_frame or figma.create_component, which could also create rectangular shapes.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or when not to use it.

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/mahmudcoding/figma-mcp'

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