Skip to main content
Glama
ArchimedesCrypto

Figma MCP Server with Chunking

list_files

Retrieve and organize files within a Figma project or team using accurate file listing, ensuring efficient management of design assets.

Instructions

List files in a project or team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID to list files from
team_idNoTeam ID to list files from

Implementation Reference

  • MCP server handler for the 'list_files' tool. It extracts arguments, calls the Figma client's listFiles method, and returns the result as JSON text content.
    case 'list_files': {
      const args = request.params.arguments as unknown as ListFilesArgs;
      console.debug('[MCP Debug] Listing files', args);
      const data = await this.figmaClient.listFiles(args);
      return {
        content: [{ type: 'text', text: JSON.stringify(data, null, 2) }],
      };
    }
  • TypeScript interface defining the input schema for list_files arguments (project_id and team_id optional). Matches the JSON inputSchema in tool registration.
    interface ListFilesArgs {
      project_id?: string;
      team_id?: string;
    }
  • src/index.ts:147-163 (registration)
    Tool registration in the ListToolsRequestHandler response. Defines name, description, and JSON inputSchema for the list_files tool.
    {
      name: 'list_files',
      description: 'List files in a project or team',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'Project ID to list files from'
          },
          team_id: {
            type: 'string',
            description: 'Team ID to list files from'
          }
        }
      }
    },
  • Implementation of listFiles method in ChunkedFigmaClient class. Performs the actual HTTP GET request to Figma's /files endpoint with optional project_id or team_id parameters.
    async listFiles(params: { project_id?: string; team_id?: string }) {
      try {
        console.debug('[MCP Debug] Listing files with params:', params);
        const response = await this.client.get('/files', { params });
        return response.data;
      } catch (error) {
        console.error('[MCP Error] Failed to list files:', error);
        throw error;
      }
    }
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. It states the action ('List files') but lacks behavioral details such as pagination, sorting, filtering options, rate limits, permissions required, or what the output format looks like. This is a significant gap 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 is appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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 tool that likely returns a list of files, the description is incomplete. It doesn't explain return values, behavioral traits, or usage context beyond the basic scope, leaving gaps for an AI agent to understand how to invoke it effectively.

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 already documents both parameters ('project_id' and 'team_id'). The description implies these are used for scoping but adds no syntax, format, or usage details beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('List') and resource ('files'), and specifies the scope ('in a project or team'). However, it doesn't differentiate from sibling tools like 'get_file_data' or 'get_file_versions', which might also retrieve file-related information but with different purposes.

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 like 'get_file_data' or 'get_file_versions'. It mentions the context ('project or team') but offers no explicit when/when-not instructions or prerequisites for selecting between 'project_id' and 'team_id'.

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/ArchimedesCrypto/figma-mcp-chunked'

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