Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set_clip_content

Toggle whether a frame clips its content to its bounds. Set clip to true to hide overflowing content, or false to display it.

Instructions

Toggle clip content on 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>",
      "clip": "<clip>"
    },
    "name": "set_clip_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYesClip content
nodeIdYesFrame node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Toggle clip content on a frame' does disclose that this is a state-changing operation on a frame's clip property. However, it does not mention side effects, return value, or that 'clip' is a boolean to be set explicitly rather than toggled from its current state.

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 a single front-loaded sentence with no filler or redundant wording. For a two-parameter boolean setter, this is appropriately concise.

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?

Given the simple tool shape and 100% schema coverage, the description is minimally viable for constructing a correct call. However, it lacks usage guidance and behavioral nuance around the boolean parameter, and with no output schema the return behavior is entirely unstated.

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 baseline is 3. The description adds no semantic detail beyond what the schema already provides: 'clip' is described as 'Clip content' and 'nodeId' as 'Frame node.' The phrase 'on a frame' merely mirrors the schema.

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?

The description uses a specific verb-resource pair ('Toggle clip content') and names the target ('on a frame'), so an agent can identify the operation. It is distinct from the many set_* siblings because 'clip content' is a unique resource, though it does not explicitly contrast with any sibling or clarify that the boolean parameter sets rather than inverts the value.

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 about when to use this tool versus set_fill, set_overflow, set_visibility, or similar setters. The only context is 'on a frame,' and no prerequisites or exclusions are mentioned.

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