Skip to main content
Glama

list-boards

Read-only

Retrieve a paginated list of Favro boards and backlogs, optionally filtered by collection or archived status.

Instructions

List Favro boards and backlogs, optionally filtered to one collection. The Favro API calls these "widgets", and each is identified by a widgetCommonId that other tools take. Type "board" is a Kanban board, type "backlog" is a card list. Results are cached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoZero-based page index. Omit for the first page. Favro returns 100 entities per page.
archivedNoReturn archived boards instead of active ones. Defaults to false.
backendIdNoRequired when page is greater than 0: the backendId from the previous call's "pagination" block, which routes the request to the same Favro server.
requestIdNoRequired when page is greater than 0: the requestId from the previous call's "pagination" block.
collectionIdNoOnly return boards that belong to this collection. Omit to list every board shared with the account.
organizationIdNoThe Favro organization to query. Defaults to the organization configured for this MCP server. Use list-organizations to discover available ids.
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. Description adds value: notes caching behavior, explains pagination indirectly via schema, and clarifies API naming. No destructive actions implied.

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?

Three sentences, no waste. Front-loaded with main purpose, each sentence adds distinct value (purpose, API explanation, behavior note).

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

Completeness4/5

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

Without an output schema, the description explains what the tool does, mentions caching, and clarifies API context. Sufficient for agent understanding, though could briefly describe return structure.

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 coverage is 100% with all parameters described. The description adds minor context (optional filter by collection, pagination hints) but does not significantly enhance meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List Favro boards and backlogs' with specific verb and resource. It distinguishes by mentioning optional collection filter and explains API terminology ('widgets', widgetCommonId).

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

Usage Guidelines4/5

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

Provides clear context for usage (list boards/backlogs, filter by collection) and mentions caching. Does not explicitly state when not to use, but sibling tools are listed for alternatives.

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/tecbay/favro-mcp'

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