Skip to main content
Glama
Sign In

Milanote MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Set card color

set_card_color
Destructive

Colour the bar on top of a note, to-do list, link, file or column, or clear it. Sets one of Milanote's eleven card colours, as the Color tool does; none removes it. Boards and images take no colour here. Editors of the board see the change at once.

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": {
      "board_id": "<board_id>",
      "card_id": "<card_id>",
      "color": "<color>"
    },
    "name": "set_card_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYesColour, or none to clear it.
card_idYesCard ID from get_board: a note, to-do list, link, file or column.
board_idYesBoard ID from list_boards, or the board URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses a real behavioral trait: “Editors of the board see the change at once,” which tells the agent the effect is immediately visible to collaborators. It also clarifies that colour is a replaceable attribute and that none clears it, consistent with destructiveHint=true. No contradiction, though idempotency behavior is not addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and card scope, then adds exclusions and effect. Mostly tight, though “as the Color tool does” is UI-referential filler that adds little for an agent.

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 simple three-parameter mutation with no output schema, the description covers scope, clearing semantics, unsupported targets and collaboration visibility. Only permission requirements and a note on repeated identical writes are missing.

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 coverage is 100% and each parameter is already documented, including the enum and the meaning of none. The description adds only the card-type restriction, which the card_id schema field already states, so it does not meaningfully exceed the baseline.

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?

States a specific verb and resource (colour the bar on top of a card, or clear it) and enumerates exactly which card types accept it. The exclusion “Boards and images take no colour here” separates it from anything else an agent might try to colour.

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?

Gives clear scope: use it for notes, to-dos, links, files and columns; use none to clear. It also states when-not-to-use via the boards/images exclusion. It stops short of naming an alternative tool for those unsupported cases or stating required permissions.

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

All Milanote MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources