Skip to main content
Glama

get_file_components

Extract reusable design components from Figma files to maintain consistency across projects and streamline UI development workflows.

Instructions

Get components from a file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileKeyYesThe key of the file to get components from

Implementation Reference

  • The core handler function that destructures the fileKey from args and calls the Figma API to retrieve components from the specified file.
    async getFileComponents(args: GetFileComponentsArgs) {
      const { fileKey } = args;
      
      return this.api.makeRequest(`/files/${fileKey}/components`);
    }
  • TypeScript interface defining the input parameters for the get_file_components tool, requiring a fileKey string.
    export interface GetFileComponentsArgs {
      fileKey: string;
    }
  • src/index.ts:361-374 (registration)
    Registers the get_file_components tool in the MCP server, including name, description, and input schema specification.
    {
      name: 'get_file_components',
      description: 'Get components from a file',
      inputSchema: {
        type: 'object',
        properties: {
          fileKey: {
            type: 'string',
            description: 'The key of the file to get components from'
          }
        },
        required: ['fileKey']
      },
    },
  • src/index.ts:570-576 (registration)
    Dispatcher in the tool request handler that validates arguments, calls the projectsHandler.getFileComponents method, and returns the result as JSON text.
    case 'get_file_components': {
      const args = this.validateArgs<GetFileComponentsArgs>(request.params.arguments, ['fileKey']);
      const result = await this.projectsHandler.getFileComponents(args);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), implying it's likely safe, but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'components' entail (e.g., structure, format). This leaves significant gaps for a tool with no 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?

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for its purpose, making it easy to parse quickly without unnecessary details.

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?

Given no annotations, no output schema, and a single parameter with full schema coverage, the description is incomplete. It doesn't explain what 'components' are, how they're returned, or any behavioral traits, leaving the agent with insufficient context for effective use beyond basic parameter passing.

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 has 100% description coverage, with fileKey documented as 'The key of the file to get components from'. The description doesn't add any meaning beyond this, such as explaining what a fileKey is or its format. Baseline 3 is appropriate since the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get components from a file' clearly states the action (get) and resource (components from a file), but it's vague about what 'components' are and doesn't distinguish from siblings like get_component (singular) or get_team_components. It provides a basic purpose without specificity.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention siblings like get_component (for a single component) or get_team_components (for team-level access), nor does it specify prerequisites such as needing a valid fileKey. Usage context is implied but not explicit.

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/smithery-ai/mcp-figma'

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