Skip to main content
Glama
the-real-talk

the-real-talk

get_clips_content

Read whether a Figma frame clips its content, returning the frame's clip-content setting by node ID.

Instructions

Read clipsContent (clip content) of a frame.

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>"
    },
    "name": "get_clips_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesID of the frame

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only lookup but says nothing about what happens if nodeId refers to a non-frame node, whether the value can be null, or what shape the response takes.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, and the redundant parenthetical gloss is a reasonable concession to unfamiliar property naming. It is terse enough that useful detail was cut rather than padded.

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 one-parameter read tool with no output schema, the description should at least indicate the return type (clipsContent is a boolean property in Figma) and the non-frame failure case. It is minimally adequate but leaves the agent guessing about the result.

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 coverage is 100% and there is only one parameter, so the schema already documents nodeId. The phrase "of a frame" does add a constraint the schema lacks — the ID must identify a frame, not an arbitrary node — but no format or example is given.

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

Purpose4/5

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

States a specific verb ("Read") and a specific resource ("clipsContent (clip content) of a frame"), and the parenthetical gloss helps decode the Figma property name. It does not explicitly contrast itself with set_clips_content, but the get/set split is inferable from the names.

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?

There is no guidance on when to call this versus alternatives such as get_node_info or get_node_raw, which likely also surface node properties. No preconditions (e.g., the node must be a frame) or exclusions are stated.

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