Skip to main content
Glama
KaiUweHella

figma-bridge-mcp

by KaiUweHella
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Local

figma_history

Read-only

Inspect private command history and compare git or Figma versions with snapshot diffs. Filter by node or file and return markdown changelogs showing what changed.

Instructions

Private command history, git/Figma versions and snapshot diff; payloads omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diffNoDiff live/latest/previous, an index, or a Figma version.
limitNoDefault 20; max 200.
formatNoDefault markdown.
nodeIdNoNode-id filter.
fileKeyNoFigma key/URL for versions.
gitPathsNoRepo-relative paths for git history.
repoPathNoRepo root for gitPaths.
includeVersionsNoMerge Figma versions via optional REST.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changedv0.6.1
    • changedInput schema / properties / diff / description
      Previous value: -"Structural diff instead of the log: what nodes were added, removed, recreated, moved or changed between two states. Refs are \"live\" (the document right now), \"latest\"/\"previous\", an index, or a Figma version id (needs the REST layer). Record comparison points with figma_run [\"history\",\"snapshot\"]."New value: +"Diff live/latest/previous, an index, or a Figma version."
    • changedInput schema / properties / diff / properties / changelog / description
      Previous value: -"Emit a markdown changelog instead of the terse report."New value: +"Return markdown changelog."
    • changedInput schema / properties / diff / properties / from / description
      Previous value: -"Older side. Default \"previous\"."New value: +"Older ref; default previous."
    • changedInput schema / properties / diff / properties / nodeId / description
      Previous value: -"Subtree root when a side is \"live\" (default: current page)."New value: +"Live subtree root."
    • changedInput schema / properties / diff / properties / to / description
      Previous value: -"Newer side. Default \"latest\". Use \"live\" for the current document."New value: +"Newer ref; default latest."
    • changedInput schema / properties / fileKey / description
      Previous value: -"File for includeVersions: bare key or full Figma URL. Default: the file open in Figma Desktop."New value: +"Figma key/URL for versions."
    • changedInput schema / properties / format / description
      Previous value: -"Output format (default markdown table)."New value: +"Default markdown."
    • changedInput schema / properties / gitPaths / description
      Previous value: -"Repo-relative file paths whose git log to merge in (generated code files)."New value: +"Repo-relative paths for git history."
    • changedInput schema / properties / includeVersions / description
      Previous value: -"Also merge the file's Figma version history (what designers saved, by whom) via the optional REST layer. Needs a configured REST token; without one a note is appended instead."New value: +"Merge Figma versions via optional REST."
    • changedInput schema / properties / limit / description
      Previous value: -"Max entries (default 20, max 200)."New value: +"Default 20; max 200."
    • changedInput schema / properties / nodeId / description
      Previous value: -"Only entries touching this node id (\"1:2\" or URL form \"1-2\")."New value: +"Node-id filter."
    • changedInput schema / properties / repoPath / description
      Previous value: -"Repo root for gitPaths (default: server working directory)."New value: +"Repo root for gitPaths."
  2. First observedv0.5.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/non-destructive, and the description adds useful behavior: 'private' scopes the history and 'payloads omitted' discloses a response constraint. It does not detail auth/rate limits or the optional REST merge, but with annotations present this is a reasonable level of disclosure.

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?

Twelve words with no filler; the opening 'Private command history' sets scope immediately and the trailing 'payloads omitted' is a high-value boundary. Every phrase earns its place.

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

Completeness2/5

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

Despite rich schema and annotations, this is an 8-parameter multi-mode tool with no output schema, and the description gives no mode-selection logic between diff, fileKey/includeVersions, and gitPaths/repoPath. It also does not clarify what 'private' entails or what the output shape looks like beyond payloads being omitted, leaving the agent to infer the intended workflow.

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 applies; to/from defaults, nodeId, fileKey, gitPaths, repoPath, format, limit, and includeVersions are already explained in the schema. The description's mention of versions and diffs maps to those parameters but adds no parameter-level detail beyond 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 names concrete resources—private command history, git/Figma versions, and snapshot diff—so an agent understands what domain the tool addresses. It lacks an explicit verb like 'retrieves' or 'lists' and does not name a sibling, but the resource set is specific enough to separate figma_history from figma_screenshot, figma_comments, and similar siblings.

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?

No sentence explains when to use this tool or when to prefer one of its sibling tools. The capability list implies a history/diff use case, but there is no exclusion guidance or alternative routing, which is important given 11 sibling tools.

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

Install Server

Other Tools