Configure a Figma frame or component to display as an overlay by setting its anchor position, scrim background, and whether clicking outside closes it.
Configure how a frame/component behaves when it is shown as an OVERLAY: where it's anchored, its scrim background, and whether clicking outside closes it.
| Name | Required | Description | Default |
|---|---|---|---|
| nodeId | Yes | ||
| overlayBackground | No | ||
| overlayPositionType | No | ||
| overlayBackgroundInteraction | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It names the configurable aspects but omits permissions, side effects, whether settings replace or merge existing values, and what happens on success or failure. For a mutation tool with four parameters, this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no wasted words. It uses a colon and parallel list to convey the three configurable aspects efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, 0% schema description coverage, and no output schema, the description should do more. It omits the required nodeId, the meaning of enum values, and whether the operation is a partial or full update, leaving key invocation details unspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It maps three of the four parameters to concepts (anchored position, scrim background, click-outside behavior), but the required nodeId is never mentioned and the enum values and color format are not explained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Configure'), the resource (overlay behavior), and enumerates the three settings it controls (anchor, scrim, outside-click). It also implicitly distinguishes itself from the sibling get_overlay_settings by being the setter.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'when it is shown as an OVERLAY' gives an implied context for use, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives like set_prototype_settings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.