Skip to main content
Glama

list-card-tasks

Read-only

Retrieve checklist items from a Favro card, showing their completion status. Optionally filter results to a single checklist using its ID.

Instructions

List the checklist items on a Favro card, with their completed state. The Favro API calls these "tasks". Takes the card's cardCommonId, and optionally a taskListId to read a single checklist. 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.
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.
taskListIdNoOnly return items from this checklist, as returned by list-card-tasklists.
cardCommonIdYesThe cardCommonId of the card whose checklist items should be listed.
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 already indicate readOnlyHint and openWorldHint. The description adds that results are not cached, providing extra transparency about freshness. No contradictions.

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, front-loaded with the action, no wasted words. Every sentence provides value.

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?

Given 6 parameters and no output schema, description covers the core purpose, optional filtering, and caching. Pagination is documented in schema, so not needed in description. Completeness is good.

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%. Description mentions the key parameters (cardCommonId, taskListId) but does not add significant meaning beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states it lists checklist items on a Favro card, including the completed state. It specifies the required cardCommonId and optional taskListId. This distinguishes it from sibling tools like list-card-tasklists.

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?

Explicitly says when to use (to list checklist items) and mentions optional filtering by taskListId. No explicit exclusions, but the purpose is clear enough to differentiate from siblings.

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