Skip to main content
Glama

list_boards

Retrieve all boards for a team to view their IDs, titles, and properties for task management.

Instructions

List all boards for a team. Returns an array of boards with their IDs, titles, and properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe team ID to list boards for (default: "0" for default team)0

Implementation Reference

  • MCP tool handler for 'list_boards': extracts teamId from input arguments (default '0'), calls focalboard.listBoards(), and returns the boards as JSON-formatted text content.
    case 'list_boards': {
      const teamId = (args?.teamId as string) || '0';
      const boards = await focalboard.listBoards(teamId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(boards, null, 2)
          }
        ]
      };
    }
  • src/index.ts:32-45 (registration)
    Registration of the 'list_boards' tool in the tools array, including name, description, and input schema definition. This array is used by the MCP server for ListToolsRequest.
    {
      name: 'list_boards',
      description: 'List all boards for a team. Returns an array of boards with their IDs, titles, and properties.',
      inputSchema: {
        type: 'object',
        properties: {
          teamId: {
            type: 'string',
            description: 'The team ID to list boards for (default: "0" for default team)',
            default: '0'
          }
        }
      }
    },
  • Input schema for the 'list_boards' tool defining the optional teamId parameter.
    inputSchema: {
      type: 'object',
      properties: {
        teamId: {
          type: 'string',
          description: 'The team ID to list boards for (default: "0" for default team)',
          default: '0'
        }
      }
    }
  • Core helper method in FocalboardClient that performs the authenticated API GET request to /teams/{teamId}/boards to fetch the list of boards.
    async listBoards(teamId: string = '0'): Promise<Board[]> {
      return this.makeRequest<Board[]>(`/teams/${teamId}/boards`);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the return format ('array of boards with their IDs, titles, and properties') which is helpful, but lacks critical details: no mention of pagination, rate limits, authentication requirements, error conditions, or whether this is a read-only operation. For a list operation with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose and includes output details. Every word contributes value, with no redundancy or fluff. It could potentially be more structured with separate usage guidance, but for its length, it's highly concise and well-formed.

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 (1 parameter, no nested objects) and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more behavioral context (e.g., read-only nature, pagination). The description covers purpose and output format but leaves operational details unspecified, making it incomplete for fully informed 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?

Schema description coverage is 100%, with the parameter 'teamId' fully documented in the schema (including default value). The description adds no parameter-specific information beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding but doesn't need to compensate for schema gaps.

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 action ('List all boards') and resource ('for a team'), with specific output details ('array of boards with their IDs, titles, and properties'). It distinguishes from siblings like 'get_board' (singular) and 'search_boards' (filtered search), but doesn't explicitly contrast them. Purpose is unambiguous but sibling differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('for a team') and suggests this is for retrieving all boards, but provides no explicit guidance on when to use this versus alternatives like 'search_boards' or 'get_board'. No prerequisites, exclusions, or comparative advice are mentioned. Usage is contextually implied but not clearly articulated.

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/gmjuhasz/focalboard-mcp-server'

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