Skip to main content
Glama

get_team_component_sets

Retrieve component sets for a specified Figma team to access and manage design system elements. Supports pagination for handling large collections.

Instructions

Get component sets for a team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYesThe team ID
page_sizeNoOptional. Number of items per page
cursorNoOptional. Cursor for pagination

Implementation Reference

  • The core handler function for the 'get_team_component_sets' tool. It extracts the team_id and pagination parameters from args, constructs the query string, and makes an API request to Figma's /teams/{team_id}/component_sets endpoint.
    async getTeamComponentSets(args: GetTeamComponentSetsArgs) {
      const { team_id, ...paginationParams } = args;
      
      const params = { ...paginationParams };
      return this.api.makeRequest(`/teams/${team_id}/component_sets${this.api.buildQueryString(params)}`);
    }
  • src/index.ts:389-410 (registration)
    Registers the tool in the MCP server's listTools response, defining its name, description, and JSON input schema matching GetTeamComponentSetsArgs.
    {
      name: 'get_team_component_sets',
      description: 'Get component sets for a team',
      inputSchema: {
        type: 'object',
        properties: {
          team_id: {
            type: 'string',
            description: 'The team ID'
          },
          page_size: {
            type: 'number',
            description: 'Optional. Number of items per page'
          },
          cursor: {
            type: 'string',
            description: 'Optional. Cursor for pagination'
          }
        },
        required: ['team_id']
      },
    },
  • TypeScript interface for input args: requires team_id, extends PaginationParams (page_size, cursor). Used for type safety in handler and validation.
    export interface GetTeamComponentSetsArgs extends PaginationParams {
      team_id: string;
    }
  • src/index.ts:586-592 (registration)
    Dispatch handler in CallToolRequestSchema switch statement: validates args, calls projectsHandler.getTeamComponentSets, and returns JSON stringified result.
    case 'get_team_component_sets': {
      const args = this.validateArgs<GetTeamComponentSetsArgs>(request.params.arguments, ['team_id']);
      const result = await this.projectsHandler.getTeamComponentSets(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 but only states the action without details on permissions, rate limits, pagination behavior, or response format. It mentions 'component sets' but doesn't clarify what that entails operationally, leaving significant gaps in understanding how the tool behaves.

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 is appropriately sized and front-loaded, 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 complexity of a read operation with pagination parameters and no output schema or annotations, the description is insufficient. It doesn't explain what 'component sets' are, how results are returned, or any behavioral traits, leaving the agent with incomplete context for effective use.

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, documenting all parameters clearly. The description adds no additional meaning beyond what the schema provides, such as explaining the relationship between 'team_id' and 'component sets' or usage tips for pagination. This meets the baseline for high schema coverage.

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 ('component sets for a team'), making the purpose understandable. However, it doesn't distinguish this tool from potential sibling tools like 'get_team_components' or 'get_file_components', which might retrieve similar resources, leaving some ambiguity about scope.

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, such as 'get_team_components' or 'get_file_components'. It lacks context about prerequisites, exclusions, or specific scenarios, offering minimal usage direction beyond the basic purpose.

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