Skip to main content
Glama
Sign In
figma-slides-mcp

figma-slides-mcp

by luan007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set Text

set_text

Update Figma Slide text nodes with new content. Automatic font loading removes the need to manually specify fonts.

Instructions

Set text content of a text node. Font loading is automatic.

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": {
      "nodeId": "<nodeId>",
      "text": "<text>"
    },
    "name": "set_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesNew text content
nodeIdYesText node ID
fontNameNoFont, e.g. "Inter Bold", "Roboto Regular"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It offers one useful behavioral trait: 'Font loading is automatic.' However, it does not mention whether existing text is replaced, how errors are handled, or any permissions required.

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 two short sentences: the first states the core purpose, the second adds a relevant behavioral note. Every word serves a function, with no unnecessary detail.

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?

The tool is a simple setter with well-documented parameters, but the description lacks context about behavior on missing nodes, whether the operation is an overwrite or append, and how it integrates with font selection. The automatic font loading note helps but does not fully cover the behavioral expectations.

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 schema already documents all parameters. The description adds no additional meaning to nodeId, text, or fontName beyond what the schema provides, so the baseline score of 3 is appropriate.

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 sets the text content of a text node, using a specific verb ('set') and resource ('text node'). This distinguishes it from siblings like set_text_range_style (which styles text ranges) and get_text_content (which reads text).

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 such as set_text_range_style or create_shape_with_text. The description simply states what it does without any contextual or exclusionary notes.

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