Milanote MCP Server and API by Cotlet

Add comment

add_comment

Destructive

Comment card on a board, or a reply in a comment thread, posted under your name. Without reply_to_id it adds a new comment card on top of the board's Unsorted panel; with it the comment joins that thread. Everyone who can open the board sees it under your name, and Milanote notifies people already in the thread. The text is plain: an @name stays text and tags nobody. Only you can edit or delete it afterwards, in Milanote. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

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>",
      "text": "<text>"
    },
    "name": "add_comment"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Comment text, plain.
`board_id`	Yes	Board ID from list_boards, or the board URL.
`reply_to_id`	No	A comment thread ID or comment ID from get_board (include_comments) to reply in. Default: a new comment card.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: visibility to everyone who can open the board, notifications to thread participants, plain-text @ handling, edit/delete restrictions, default confirmation, and owner approval. These details go well beyond readOnly, destructive, openWorld, and idempotent hints.

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?

The description is front-loaded with the core action and placement behavior, and most sentences carry useful operational detail. It is slightly verbose and repeats the 'under your name' visibility point, but there is no major waste.

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 mutating comment-creation tool with no output schema, the description covers placement, visibility, notifications, text semantics, post-creation edit/delete behavior, confirmation, and approval. An agent has enough context to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for reply_to_id by explaining that omitting it places a new card on the Unsorted panel and including it joins an existing thread. It adds less for board_id and text beyond the schema, so it is not a full 5.

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: it adds a comment card or a reply in a comment thread. It clearly distinguishes the two modes via reply_to_id, so an agent can identify the action without opening the schema.

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 explicitly says that without reply_to_id the call creates a new comment card on the Unsorted panel, and with it the comment joins a thread. It does not name sibling tools such as edit_comment or delete_comment as alternatives, but the usage condition for its own parameters is clear.

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 tools Inspect

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.