Skip to main content
Glama
Sign In
@echobt/figma-mcp

@echobt/figma-mcp

by echobt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_page_contents

Retrieve all top-level frames and their immediate children from a specific page in a Figma .fig file for offline design extraction.

Instructions

Get the contents of a specific page, including all top-level frames and their immediate children.

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": {
      "filePath": "<filePath>",
      "pageName": "<pageName>"
    },
    "name": "get_page_contents"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesPath to the .fig file
pageNameYesName of the page to get contents for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, placing full burden on the description. While it mentions returning frames and children, it omits details like whether return is read-only, permissions needed, or depth of returned hierarchy.

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?

A single, focused sentence with no wasted words. Could be slightly more informative without harming conciseness, but it's efficient.

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?

With no output schema, the description should clarify what 'contents' means (e.g., node names, properties, layout data). It lacks details on return structure, making it incomplete for a tool returning hierarchical data.

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?

Both parameters are fully described in the schema (100% coverage). The description adds no extra meaning beyond what the schema already provides, so baseline 3 applies.

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 clearly states the tool retrieves page contents, including top-level frames and immediate children. This verb+resource+scope specification distinguishes it from siblings like get_document_summary or get_tree_summary.

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

Usage Guidelines3/5

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

The description implies usage for fetching page contents, but provides no explicit guidance on when to use versus alternatives (e.g., get_node_details, list_pages) or when not to use it.

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