Skip to main content
Glama

extract-one-component

Extract a single component from Figma designs to generate corresponding React Native code with proper typing and styling.

Instructions

Extract a single component from Figma file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersYes

Implementation Reference

  • Handler implementation for the extract-one-component tool. Fetches Figma data and invokes generateComponent with componentName parameter.
    async ({ parameters: { componentName } }, extra) => {
      try {
        // Fetch Figma file data
        logger.info('Fetching Figma file data...')
    
        // const data = await response.json()
        const data = await fetchFigmaData()
        logger.info('Successfully fetched Figma file data')
    
        // Process the component data
        const result = await generateComponent(data, true, componentName)
        logger.info('Component extraction successful')
    
        // Return the result to the client
        return {
          componentsData: result.componentSets, // Pass the structured component data
          content: [
            {
              type: 'text' as const,
              text: result.message,
            },
          ],
        }
      } catch (error: any) {
        logger.error(`Error extracting component ${componentName}:`, error)
        return {
          isError: true,
          content: [
            {
              type: 'text' as const,
              text: `Error extracting component ${componentName}: ${error.message}`,
            },
          ],
        }
      }
    }
  • Input schema using Zod: object with componentName: string
    {
      parameters: z.object({
        componentName: z.string(),
      }),
  • src/index.ts:145-152 (registration)
    MCP server.tool registration for 'extract-one-component', including description and schema reference.
    server.tool(
      'extract-one-component',
      'Extract a single component from Figma file',
      {
        parameters: z.object({
          componentName: z.string(),
        }),
      },
  • Core logic for generating component data from Figma document, with filtering for specific component when componentToExtract provided (used as third arg for single component extraction).
    export async function generateComponent(
      component: any,
      validation: boolean = false,
      componentToExtract: string = ''
    ) {
      try {
        const { document } = component
        const componentsPage = document.children.find(
          (c: any) => c.name === 'Components'
        )
    
        if (!componentsPage) {
          console.log('No Components page found in document')
          throw new Error('Components page not found in Figma file')
        }
    
        const page = componentsPage.children
        let componentSets = []
        let processedCount = 0
        const checkExisting = (componentName: string) =>
          validation ? !existsSync(`${componentDir}/${componentName}`) : true
    
        const specificComponent = (
          componentName: string,
          componentToExtract: string
        ) =>
          componentToExtract
            ? areSameComponent(componentName, componentToExtract)
            : true
    
        for (const section of page) {
          const { children } = section
          if (!children) continue
    
          for (const item of children) {
            const { type, name } = item
            const componentName = toPascalCase(name)
    
            if (
              type === 'COMPONENT_SET' &&
              checkExisting(componentName) &&
              specificComponent(componentName, componentToExtract)
            ) {
              processedCount++
    
              try {
                const props = extractComponentProps(item.children)
    
                const minified = {
                  name: componentName,
                  props,
                  children: extractComponentChildren(item.children),
                }
                componentSets.push(minified)
              } catch (processError) {
                return {
                  message: `Error processing component ${name}: ${processError}`,
                  componentSets: [],
                }
              }
            }
          }
        }
    
        // Create a formatted result for the user
        const message = `Successfully processed ${processedCount} components.\n\nComponent sets: ${componentSets.length}\nComponent paths:\n${componentSets.map((cs) => `- ${cs.name}`).join('\n')}`
    
        // Return both the result message and the component data
        return {
          message,
          componentSets,
        }
      } catch (error) {
        console.error(`Error generating component: ${error}`)
        throw error
      }
    }
  • fetchFigmaData: retrieves Figma file JSON data via API, called by the tool handler.
    export async function fetchFigmaData() {
      const response = await fetch(`https://api.figma.com/v1/files/${FIGMA_FILE}`, {
        headers: {
          'X-Figma-Token': FIGMA_TOKEN,
        },
      })
    
      if (!response.ok) {
        const errorText = await response.text()
        return {
          isError: true,
          content: [
            {
              type: 'text' as const,
              text: `Failed to fetch Figma file: ${response.status} ${response.statusText} - ${errorText}`,
            },
          ],
        }
      }
    
      return await response.json()
    }
Behavior1/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 of behavioral disclosure. However, it only states the action without any details on permissions, side effects, rate limits, or output format. For a tool with no annotations, this minimal description fails to provide essential behavioral context.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for its content, making it easy to parse quickly.

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 the tool's complexity (1 parameter with nested objects, no annotations, no output schema), the description is incomplete. It lacks details on behavior, parameter usage, and output, which are critical for an agent to use the tool effectively in context with its siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the tool description doesn't add any parameter semantics. It doesn't explain what 'componentName' represents (e.g., format, examples, or constraints), leaving the parameter's meaning unclear beyond the schema's basic type definition.

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 states the tool's purpose ('Extract a single component from Figma file') with a clear verb ('Extract') and resource ('component from Figma file'), but it doesn't distinguish from sibling tools like 'extract-components' or 'extract-latest-components'. The purpose is understandable but lacks specificity about what makes this tool unique compared to its 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or specify scenarios where extracting a single component is preferred over batch extraction (e.g., 'extract-components'), leaving the agent without context for tool selection.

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/kailashAppDev/figma-mcp-toolkit'

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