Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by JulianKerignard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_cards_by_due_date

Retrieve all cards with due dates from a board, sorted by urgency to quickly identify upcoming or overdue tasks.

Instructions

Liste toutes les cartes d'un board qui ont une date limite, triées par échéance (les plus urgentes en premier)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "boardId": "<boardId>"
    },
    "name": "list_cards_by_due_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesParameter boardId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully reveals that only cards with a due date are returned and that sorting is by soonest due date first. It does not mention read-only nature, pagination, or what card fields are included, but the core behavior is clear.

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?

One efficient, front-loaded sentence that states the resource, filter, and sorting behavior with zero filler. The parenthetical clarifies the sort order without adding bulk.

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?

For a single-parameter read-style tool, the description is sufficiently complete: it identifies the board scope, the due-date filter, and the ordering. It does not describe output fields, but this is acceptable given the simple nature of the tool and the absence of an output schema.

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% and the schema already documents boardId as a 24-character string. The description adds the semantic context that boardId refers to the board whose due-dated cards are listed, but it does not need to add more.

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 names a specific verb ('Liste'), a specific resource ('cartes d'un board'), and a clear filter ('qui ont une date limite') with sorting behavior. This clearly distinguishes it from sibling tools like list_trello_cards or set_card_due_date.

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 intended use is implied: use this when you need a board's due-dated cards ordered by urgency. However, it does not explicitly state when to prefer this over list_trello_cards, search_trello_cards, or get_member_cards, nor does it mention exclusion cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools