Skip to main content
Glama
enthouan

trello-mcp

by enthouan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

card_actions

Retrieve and audit a Trello card's action history and comments, using filters, limits, and paging to review recent activity or navigate large histories.

Instructions

Use when auditing recent activity or comments for a card; use filter, limit, page, since, before, and fields to page large histories.

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based result page for Trello action collections.
limitNoMaximum number of Trello objects to return; Trello caps this at 1000.
sinceNoISO-8601 date, Mongo id, or null cursor for Trello since/before paging.
beforeNoISO-8601 date, Mongo id, or null cursor for Trello since/before paging.
cardIdYesTrello card id, short link, or Trello card URL.
fieldsNoComma-separated Trello action fields to request; use all for detailed follow-up reads. Schema-required fields are added automatically.id,type,date,data,idMemberCreator
filterNoTrello action filter such as all or commentCard.all
memberNoWhether to include member objects on actions.
memberFieldsNoComma-separated Trello member fields when member is true.username,fullName,initials,avatarUrl
memberCreatorNoWhether to include the memberCreator object on actions.
memberCreatorFieldsNoComma-separated Trello memberCreator fields when memberCreator is true.username,fullName,initials,avatarUrl

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Auditing' implies a read-oriented operation, and it discloses that filter, limit, page, since, before, and fields support paging large histories, but it does not explicitly confirm read-only behavior, permissions, or result shape.

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?

The description is a single compact sentence with the primary use case front-loaded and no wasted text. The paging guidance is also placed where it is immediately useful.

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?

The tool has 11 parameters and no output schema, but the description only covers the auditing use case and basic paging. The schema fills in parameter details, yet the description does not explain the return payload or the member/memberCreator expansion options, leaving some contextual gaps.

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%, so the schema already explains the parameters in detail. The description names several paging/filtering parameters but adds little semantic depth beyond what the schema provides, making the baseline 3 appropriate.

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 scopes the tool to card-level activity/comment auditing, which distinguishes it from board_actions, list_actions, and workspace_actions. It does not explicitly state a verb like 'list' or 'retrieve', but the intended operation is still easy to infer.

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?

It gives a clear use case: auditing recent activity or comments for a card. It also points to paging-related parameters for large histories, but it does not mention when to choose card_actions over sibling activity tools such as board_actions or list_actions.

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