Skip to main content
Glama
Sign In
Milanote MCP Server

Milanote MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Set card color

set_card_color
Idempotent

Set or clear the colour bar on a Milanote note, to-do list, link, file or column so cards are visually grouped and easy to scan; pass none to remove the colour.

Instructions

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 observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare mutation, idempotence, non-destructiveness, and open-world behavior. The description adds useful behavioral detail: `none` removes the color, unsupported card types are excluded, and editors see the change immediately, though it does not discuss permissions or error behavior.

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 three compact sentences and front-loads the main operation. Every sentence contributes useful scoping, clearing behavior, or collaboration context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-required-parameter mutation tool with full schema coverage, annotations, and no output schema, the description supplies enough context to call it correctly. Supported types, exclusions, clearing behavior, and immediate visibility are all covered.

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 the enum plus parameter descriptions already document `color`, `card_id`, and `board_id` well. The description adds only light reinforcement about the color applying to the top bar and `none` clearing it, so it does not materially exceed the schema.

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 states a specific verb and resource: coloring the bar on top of supported card types, or clearing it. It also names exclusions (boards and images) and clarifies the effect of `none`, so an agent can distinguish this from unrelated board-editing siblings.

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 clearly indicates supported card types and when clearing applies, which is strong context for usage. It does not explicitly name alternatives or compare to operations like labels, so it falls short of full when/when-not guidance.

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