Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by GabrielRamirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Notifications

get_notifications

Retrieve your Trello notifications with optional filters for read status and result count. Use this tool to check updates on boards, cards, and activity.

Instructions

Get notifications for the authenticated user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of notifications (default: 50, max: 1000)
readFilterNoFilter by read status (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations present, the description must carry the behavioral transparency burden. It only says 'get' and 'authenticated user'; it does not disclose whether fetching notifications affects read state, how results are ordered, or what the response looks like.

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 concise sentence with no filler. The verb and resource are front-loaded, and every word earns its place.

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?

For a simple read tool with optional parameters, the description is minimally adequate. However, with no output schema and no annotations, it leaves behavioral details (e.g., read-state side effects, response format) unspecified.

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 fully documents both limit and readFilter. The description adds no parameter-level meaning, making the baseline of 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 uses a specific verb ('get') and resource ('notifications'), and clarifies the scope to the authenticated user. It clearly identifies what the tool does, though it does not explicitly contrast with sibling mark_all_notifications_read.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives. While mark_all_notifications_read is a related sibling, the description provides no explicit routing or exclusions.

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