Skip to main content
Glama

list-cards

Read-only

List Favro cards from a board, collection, todo list, or by ID. Narrow results with column or card scopes for current data.

Instructions

List Favro cards on a board, in a collection, or in the account's todo list. You must scope the call with one of widgetCommonId, collectionId, cardCommonId, cardSequentialId, or todoList. columnId narrows the results further but cannot be used on its own. Card descriptions are truncated here; use get-card for the full text. Not cached, so results are always current.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoZero-based page index. Omit for the first page. Favro returns 100 entities per page.
uniqueNoReturn each card only once even when it appears on several boards. Defaults to false.
archivedNoReturn archived cards instead of active ones. Defaults to false.
columnIdNoNarrow the results to a single column. Must be combined with widgetCommonId.
todoListNoReturn cards from the authenticated user's todo list. One of the accepted scopes.
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.
cardCommonIdNoReturn every instance of this card across boards. One of the accepted scopes.
collectionIdNoReturn cards in this collection. One of the accepted scopes.
organizationIdNoThe Favro organization to query. Defaults to the organization configured for this MCP server. Use list-organizations to discover available ids.
widgetCommonIdNoReturn cards on this board. One of the accepted scopes.
cardSequentialIdNoReturn the card with this human-readable sequential id. One of the accepted scopes.
descriptionFormatNoFormat of the card description. Defaults to "plaintext".
Behavior4/5

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

Annotations already mark readOnlyHint and openWorldHint. Description adds 'Not cached, so results are always current' and truncation behavior, providing context beyond annotations without contradiction.

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?

Four concise sentences front-loading purpose, then constraints, then behavioral notes. No fluff or repetition.

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?

Covers scoping, truncation, and caching. Lacks mention of return structure or pagination details, but given no output schema and annotations present, the description is mostly adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is documented. Description adds relationships (e.g., columnId must be combined with widgetCommonId) and scoping rules, enhancing understanding beyond the schema alone.

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 the tool lists Favro cards on a board, collection, or todo list, with a specific verb and resource. It distinguishes from siblings like get-card and search-cards by mentioning truncation and scoping.

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

Usage Guidelines5/5

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

Explicitly states required scoping parameters and that columnId cannot be used alone. Mentions that descriptions are truncated and get-card should be used for full text, providing clear when-to-use and when-not-to.

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