Skip to main content
Glama

get_team_projects

Retrieve Figma projects for a specific team, supporting pagination to manage large collections efficiently.

Instructions

Get projects 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 main handler function for the 'get_team_projects' tool. It extracts the team_id and pagination parameters from args, constructs the API endpoint with query string, and calls FigmaApi.makeRequest to fetch the projects.
    async getTeamProjects(args: GetTeamProjectsArgs) {
      const { team_id, ...paginationParams } = args;
      
      const params = { ...paginationParams };
      return this.api.makeRequest(`/teams/${team_id}/projects${this.api.buildQueryString(params)}`);
    }
  • src/index.ts:291-311 (registration)
    Registration of the 'get_team_projects' tool in the MCP server's listTools response, including name, description, and input schema.
    {
      name: 'get_team_projects',
      description: 'Get projects 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 defining the input arguments for getTeamProjects, extending PaginationParams with required team_id.
    export interface GetTeamProjectsArgs extends PaginationParams {
      team_id: string;
    }
  • src/index.ts:546-552 (registration)
    Dispatch handler in the CallToolRequest that routes 'get_team_projects' calls to the projectsHandler.getTeamProjects method.
    case 'get_team_projects': {
      const args = this.validateArgs<GetTeamProjectsArgs>(request.params.arguments, ['team_id']);
      const result = await this.projectsHandler.getTeamProjects(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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Get') but doesn't add context beyond that—missing details like whether it's read-only (implied but not explicit), pagination behavior (hinted by parameters but not explained), rate limits, authentication needs, or error handling. The description is minimal and fails to compensate for the lack of annotations.

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—'Get projects for a team' is front-loaded and appropriately sized for its purpose. It avoids unnecessary words and gets straight to the point, 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 (a read operation with pagination parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'projects' entail, the return format, or how to handle pagination, leaving gaps that could hinder an AI agent's ability to use the tool effectively. It should provide more context to compensate for missing structured data.

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%, with clear descriptions for team_id, page_size, and cursor. The description doesn't add any meaning beyond the schema, such as explaining how pagination works or what format the team_id should be in. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra value is provided.

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 projects for a team' states the basic action (get) and resource (projects for a team), but it's vague about scope (e.g., all projects, active projects, or filtered ones) and doesn't distinguish it from sibling tools like 'get_project_files' or 'get_team_components'. It avoids tautology by not restating the name exactly, but lacks 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 prerequisites (e.g., needing a valid team_id), exclusions, or how it differs from similar tools in the sibling list, such as 'get_project_files' which might handle files within projects. Usage is implied only by the name and description.

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