Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export frames to PDF

figma_export_frames_to_pdf
Read-only

Export frames to one multi-page PDF, one frame per page, in the order of nodeIds. In a Figma Slides file, deck: true instead exports every slide in presentation order, leaving out skipped slides unless includeSkipped; the result…

Instructions

Export frames to one multi-page PDF, one frame per page, in the order of nodeIds. In a Figma Slides file, deck: true instead exports every slide in presentation order, leaving out skipped slides unless includeSkipped; the result lists slideIds in page order. Each frame is rendered by the plugin and the pages are merged by the bridge. A frame that cannot be rendered is reported in failed[] and the rest still merge — an unreadable page is worse than a missing one, so nothing is silently substituted. final: true marks the delivery: under BRIDGE_PROCESS=strict every page that belongs to a brief needs a passing figma_sign_off newer than its last change.

Input Schema

NameRequiredDescriptionDefault
deckNoFigma Slides: true exports every slide of the deck, in order, instead of nodeIds.
finalNoThe delivery. Under BRIDGE_PROCESS=strict a node that belongs to a brief needs a passing figma_sign_off newer than its last change. Default false: a render to judge, never gated.
nodeIdsNoFrames to export, in page order. Not with `deck`.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
outputPathYesWhere to write the merged PDF. Same path rules as `figma_export_node`'s `saveTo`.
includeSkippedNoWith deck: also the slides skipped in the presentation. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / final
      Added value: +{
+  "description": "The delivery. Under BRIDGE_PROCESS=strict a node that belongs to a brief needs a passing figma_sign_off newer than its last change. Default false: a render to judge, never gated.",
+  "type": "boolean"
+}
  2. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: rendering is split between plugin and bridge, partial failures land in `failed[]` and the rest still merge, and `final: true` is gated by figma_sign_off under BRIDGE_PROCESS=strict. This tells the agent exactly what happens on partial failure and what the strict-mode precondition is, which annotations alone could not convey.

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?

Front-loaded with the core export behavior, then deck mode, then failure handling, then delivery gating. Dense em-dash clauses make it harder to skim, but every sentence carries real information rather than restating the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fills the gap by describing the returned `failed[]` and `slideIds` fields and their ordering. For a 6-param export tool with a partial-failure model, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema lacks: nodeIds defines page order, deck enumerates slides in presentation order, and the result reports `slideIds` in page order. The `final` and `session` params get slightly weaker treatment in the prose, keeping it from a 5.

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

Purpose5/5

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

States a specific verb and resource plus the output shape: 'Export frames to one multi-page PDF, one frame per page, in the order of `nodeIds`.' The deck-mode clause further scopes the Slides variant, which clearly separates it from single-node siblings like figma_export_node.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete routing rules: nodeIds for frames, `deck: true` for Slides files, `includeSkipped` only with deck, and `final: true` reserved for delivery. It never explicitly names a required alternative tool (e.g. 'for a single node use figma_export_node'), only nodding at it via the outputPath path-rule reference, so it falls just short of a 5.

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