Skip or include specific slides during Figma presentations. Toggle the visibility of any slide by providing its unique ID and skip status.
Toggle whether a slide is skipped during presentation mode.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | Yes | True to skip the slide, false to include it | |
| slideId | Yes | The node ID of the slide |
Changes observed during successful MCP inspections.
v1.46.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It identifies the mutation as a toggle, but does not disclose permission requirements, side effects, reversibility guarantees, or return behavior for the operation.
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?
The description is a single, front-loaded sentence with no wasted words. It states the operation and its context immediately.
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?
Given the low complexity of two required parameters, the description is minimally adequate. However, with no annotations and no output schema, it leaves open whether the tool returns the updated slide state or requires any special presentation-mode preconditions.
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 coverage is 100%, and both parameters are fully documented in the schema, including the boolean semantics for skip and the node ID for slideId. The description adds no parameter details beyond what the schema already provides, so the baseline of 3 applies.
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?
The description states a clear verb and resource: toggling whether a slide is skipped during presentation mode. It is specific enough to distinguish from slide retrieval, creation, and transition tools, though it does not explicitly contrast with related siblings like figma_focus_slide.
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 presentation-mode context implies when the tool is useful, but there are no explicit when-to-use/when-not-to-use guidelines or named alternatives among the many slide-related siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.