Skip to main content
Glama
deenesjakoruzh
f2c-ai

f2c-mcp-server

by f2c-ai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

figma_get_file_meta

Retrieve metadata for a Figma file by providing its unique file key and personal access token. Streamline design file analysis and integration.

Instructions

Get metadata information for a Figma file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileKeyYesUnique identifier of the Figma file
personalTokenNoYour Figma personal access token

Implementation Reference

  • src/server/figma/tools/figma.ts:95-114 (registration)
    Registration of the figma_get_file_meta tool (commented out), including Zod input schema, description, and inline handler that calls api.meta(o).
    // server.tool(
//   'figma_get_file_meta',
//   'Get metadata information for a Figma file',
//   {
//     fileKey: z.string().describe('Unique identifier of the Figma file'),
//     personalToken: z.string().optional().describe('Your Figma personal access token'),
//   },
//   async (o): Promise<CallToolResult> => {
//     try {
//       const data = await api.meta(o)
//       return {
//         content: [{type: 'text', text: JSON.stringify(data)}],
//       }
//     } catch (error: any) {
//       return {
//         content: [{type: 'text', text: `Error: ${error.message}`}],
//       }
//     }
//   },
// )
  • src/server/figma/tools/figma.ts:102-113 (handler)
    Tool handler function: invokes api.meta(o), stringifies the result as JSON text, or returns error message.
    //   async (o): Promise<CallToolResult> => {
//     try {
//       const data = await api.meta(o)
//       return {
//         content: [{type: 'text', text: JSON.stringify(data)}],
//       }
//     } catch (error: any) {
//       return {
//         content: [{type: 'text', text: `Error: ${error.message}`}],
//       }
//     }
//   },
  • src/server/figma/apis/figma.ts:28-32 (helper)
    Helper method in FigmaRestApi class that constructs the /files/{fileKey}/meta URL and fetches the metadata using the configured token.
    // Returns the metadata for the file referred to by :key
async meta(o: GetKeyParams) {
  const url = this.opToUrl(`${this.figmaHost}/files/${o.fileKey}/meta`, o)
  return this.fetch(url)
}
  • src/server/figma/types/figma.ts:24-27 (schema)
    TypeScript interface defining parameters for the meta API: required fileKey and optional personalToken.
    export interface GetKeyParams {
  fileKey: string
  personalToken?: string
}

Tool Definition Quality

B3.1/5.0
Behavior2/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. It states it's a 'Get' operation, implying read-only, but doesn't clarify authentication needs (though the schema hints at 'personalToken'), rate limits, error handling, or what metadata is included. 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, clear sentence with zero waste. It's appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary details.

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

Completeness3/5

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

Given the tool's low complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks behavioral details and usage context, making it incomplete for optimal agent operation without additional inference.

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 schema fully documents the two parameters ('fileKey' and 'personalToken'). The description adds no additional meaning beyond what the schema provides, such as examples or context for the parameters, but the baseline is 3 when schema coverage is high.

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 clearly states the verb ('Get') and resource ('metadata information for a Figma file'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'figma_get_file_data' or 'figma_get_images', which likely retrieve different types of file information, so it doesn't reach the highest score.

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 contexts where this metadata retrieval is preferred over other file-related operations, leaving the agent to infer usage based on tool names alone.

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

Related 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/f2c-ai/f2c-mcp'

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