Skip to main content
Glama
neozhehan

Figma Edit MCP

by neozhehan
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

List Components

component_list
Read-only

List Figma components with filtering by origin (local/remote) and scope (page/document). Document scans report page failures in coverage; page-scoped queries return structured errors.

Instructions

List components in the document, with filtering and scope options. Document scans isolate page failures and report them in coverage; page-scoped failures return their structured error directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoScope of the search: 'page' (queries a specific page, requiring pageId) or 'document' (entire file, default).document
filterNoFilter components by origin: 'local' (created in this file) or 'remote' (library components). If omitted, returns all.
pageIdNoThe ID of the page to query when scope is 'page'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoTotal count of components
errorNo
coverageNoPage-scan coverage; partial read data remains usable when complete is false
componentsNoList of component objects

Schema Changelog

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

  1. Changed3 schema fields changedv2.3.3
    • addedOutput schema / properties / coverage
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "complete": {
+          "const": true,
+          "description": "Every attempted page succeeded",
+          "type": "boolean"
+        },
+        "pageErrors": {
+          "description": "Empty: no page failed",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "error": {
+                "additionalProperties": false,
+                "description": "Structured per-page failure",
+                "properties": {
+                  "code": {
+                    "description": "Stable machine-readable failure code (see the error playbook)",
+                    "type": "string"
+                  },
+                  "details": {
+                    "description": "Optional structured context (e.g. partialMutation, before-values)"
+                  },
+                  "message": {
+                    "description": "Human/agent-readable message embedding its own recovery",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "code",
+                  "message"
+                ],
+                "type": "object"
+              },
+              "pageId": {
+                "description": "ID of the page that could not be loaded, resolved, or read",
+                "type": "string"
+              }
+            },
+            "required": [
+              "pageId",
+              "error"
+            ],
+            "type": "object"
+          },
+          "maxItems": 0,
+          "type": "array"
+        },
+        "pagesAttempted": {
+          "description": "Distinct pages this call tried to resolve, load, or read. 0 means the result required no page access at all — it does NOT mean the document was checked and found clean.",
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "complete",
+        "pagesAttempted",
+        "pageErrors"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "complete": {
+          "const": false,
+          "description": "At least one attempted page failed",
+          "type": "boolean"
+        },
+        "pageErrors": {
+          "description": "Structured failures for pages omitted from this result; successful pages are still returned",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "error": {
+                "additionalProperties": false,
+                "description": "Structured per-page failure",
+                "properties": {
+                  "code": {
+                    "description": "Stable machine-readable failure code (see the error playbook)",
+                    "type": "string"
+                  },
+                  "details": {
+                    "description": "Optional structured context (e.g. partialMutation, before-values)"
+                  },
+                  "message": {
+                    "description": "Human/agent-readable message embedding its own recovery",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "code",
+                  "message"
+                ],
+                "type": "object"
+              },
+              "pageId": {
+                "description": "ID of the page that could not be loaded, resolved, or read",
+                "type": "string"
+              }
+            },
+            "required": [
+              "pageId",
+              "error"
+            ],
+            "type": "object"
+          },
+          "minItems": 1,
+          "type": "array"
+        },
+        "pagesAttempted": {
+          "description": "Distinct pages this call tried to resolve, load, or read. 0 means the result required no page access at all — it does NOT mean the document was checked and found clean.",
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "complete",
+        "pagesAttempted",
+        "pageErrors"
+      ],
+      "type": "object"
+    }
+  ],
+  "description": "Page-scan coverage; partial read data remains usable when complete is false"
+}
    • addedOutput schema / properties / error
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "description": "Stable machine-readable failure code (see the error playbook)",
+      "type": "string"
+    },
+    "details": {
+      "description": "Optional structured context (e.g. partialMutation, before-values)"
+    },
+    "message": {
+      "description": "Human/agent-readable message embedding its own recovery",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
    • removedOutput schema / required
      Removed value: -[
-  "count",
-  "components"
-]
  2. Changed1 schema field changedv2.3.2
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
  3. Changed1 schema field changedv2.3.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / pageId
      Added value: +{
+  "description": "The ID of the page to query when scope is 'page'",
+  "type": "string"
+}
    • changedInput schema / properties / scope / default
      Previous value: -"current_page"New value: +"document"
    • changedInput schema / properties / scope / description
      Previous value: -"Scope of the search: 'current_page' (default) or 'document' (entire file, streams progress page-by-page)."New value: +"Scope of the search: 'page' (queries a specific page, requiring pageId) or 'document' (entire file, default)."
    • changedInput schema / properties / scope / enum
      Previous value: -[
-  "current_page",
-  "document"
-]New value: +[
+  "page",
+  "document"
+]
  5. Addedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only and open-world behavior, but the description adds valuable context: document scans report failures via a 'coverage' field, while page-scoped scans return structured errors directly. This explains edge-case behavior beyond what the annotations provide.

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?

The description is only two sentences long. The first sentence states the core purpose and capabilities; the second provides a concise behavioral nuance about error handling. Every phrase earns its place with no fluff or repetition.

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

Completeness4/5

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

The tool is straightforward with optional parameters, and an output schema exists so return values are documented there. The description explains the key difference between document and page scope error behavior, which is essential for correct usage. It lacks nothing critical for an AI agent to invoke it properly.

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?

The input schema covers 100% of parameter descriptions, so the description is not required to repeat them. It does reference 'filtering and scope options' generically, which aligns with the schema but adds no new detail. Given the schema coverage, a baseline of 3 is appropriate.

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 opens with a clear verb and resource: 'List components in the document.' It explicitly mentions filtering and scope options, and the additional detail about failure reporting distinguishes it from generic list tools. This leaves no ambiguity about what the tool does.

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 states the primary use case (listing components) and even distinguishes between document and page scope behaviors. It does not explicitly name alternative tools or say when not to use it, but the resource is so specific that confusion with sibling list tools (style_list, variable_list) is unlikely.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/neozhehan/figma-edit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server