figma-unlimited-mcp

Overview Schema Source Related Servers Discussions Admin

Create text nodes

create_texts

Add free-floating text to FigJam for board titles, column headers, and annotations. Specify content, position, color, and font size directly.

Instructions

Add free-floating text. Good for board titles, column headers and annotations; use stickies for content the user will rearrange.

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": {
      "items": "<items>"
    },
    "name": "create_texts"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. It only states the primary action and typical use cases, but does not mention return values, permissions, side effects, or error behavior. The 'free-floating' hint is useful but 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.

Conciseness5/5

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

Two concise, front-loaded sentences. The action is stated first, followed by guidance and a distinguishing alternative. No wasted words.

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

Completeness3/5

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

For a simple creation tool with a rich input schema, the description is mostly complete on purpose and usage, but it omits return value behavior and failure/side-effect details. Since no output schema is provided, the description could have explained what the API returns on success.

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

Parameters2/5

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

Description has 0% parameter coverage. While the input schema contains detailed property descriptions, the tool description itself adds no parameter semantics, so it fails to compensate for the low coverage as required.

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 uses a specific verb ('Add') and resource ('free-floating text') and immediately distinguishes from stickies by naming use cases (board titles, column headers, annotations). This clearly sets it apart from sibling tools like create_stickies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool ('Good for board titles, column headers and annotations') and provides an alternative ('use stickies for content the user will rearrange'). This gives clear when-to-use and when-not-to-use guidance.

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