Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_upload_assets

Import local PNG, JPG, GIF or WEBP files into Figma as image-filled rectangles, or apply an image as the fill of an existing node—bridging local assets and your design file in one call.

Instructions

Import local image files (PNG/JPG/GIF/WEBP) into Figma as rectangles with an image fill, or apply one as the fill of an existing node.

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": {
      "paths": "<paths>"
    },
    "name": "figma_upload_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
pathsYesAbsolute paths of image files
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.
parentIdNoWhere to place new rectangles (default: current page)
scaleModeNoFILL
targetNodeIdNoApply the first image as this node's fill instead of creating a rectangle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the write nature of the operation and implies that targeting an existing node replaces that node's fill, but it says nothing about required write permissions, whether the previous fill is destroyed or recoverable, or what happens when a path is invalid or the 20-file cap is exceeded. Those omissions matter for a document-mutating tool with zero annotation coverage.

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?

A single front-loaded sentence that states the input formats and both outcomes with no filler or repetition. Nothing could be removed without losing information.

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 7-parameter mutation tool with no annotations and no output schema, the definition covers the core modes but leaves the agent guessing about return values (presumably created node IDs) and about the coordinate/scale parameters. It is adequate to attempt a call but not complete enough to call it confidently in fill mode.

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 57%, and the description adds genuine meaning beyond the schema by naming the supported image formats (the paths field only says 'image files') and by clarifying that in fill mode only the first image is used. However, x, y, scaleMode, and parentId semantics are left entirely to the schema, and the interaction between parentId and targetNodeId is not addressed.

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?

The description gives a specific verb (import), a specific resource (local image files, with the four accepted formats enumerated), and the resulting artifact (rectangles with an image fill, or a fill applied to an existing node). This is the clear inverse of figma_download_assets and cannot be confused with any read-only sibling, so an agent can select it from the name plus description alone.

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?

The description establishes the two operating modes and implicitly ties mode selection to whether you want a new rectangle or to refill an existing node, which is useful routing guidance. It stops short of explicit when-not-to-use guidance — no mention of what to do if a file is already uploaded, or of any prerequisite about connecting a file before calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.