Skip to main content
Glama
the-real-talk

the-real-talk

set_clips_content

Toggles clipping for a Figma frame so child content is either clipped to the frame bounds or allowed to overflow.

Instructions

Set 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>",
      "clipsContent": "<clipsContent>"
    },
    "name": "set_clips_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesID of the frame
clipsContentYestrue to clip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 behavioral burden for a mutation. It does not disclose whether non-frame nodes cause an error, whether the change is undoable, whether child layers are affected, or whether the operation is idempotent.

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 short sentence with the target object front-loaded and no wasted clauses. It is efficient, though the parenthetical '(clip content)' is mildly redundant with the field name.

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 two-parameter setter with full schema coverage and no output schema, the description is minimally adequate. It omits the node-type constraint and any error behavior, which matter for a mutation with no annotations backing it up.

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 both parameters are already documented in the schema and the baseline is 3. The phrase 'of a frame' adds a small hint that nodeId should reference a frame-type node, which is meaning beyond the schema's generic 'ID of the frame'.

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 names a specific verb ('Set') and resource ('clipsContent ... of a frame'), so the operation is identifiable. However, it largely restates the tool name and parameter name, and it offers no differentiation from the sibling get_clips_content beyond the implicit set/get distinction.

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 use this tool versus reading the value with get_clips_content, and no stated prerequisites such as the node needing to be a frame. The agent must infer usage entirely from the name.

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