Skip to main content
Glama
Sign In
Milanote MCP Server

Milanote MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delete comment

delete_comment
Destructive

Permanently remove a comment you posted from a Milanote board thread, while keeping the thread and other comments intact. Use board_id and comment_id; deletion cannot be undone.

Instructions

Delete a comment you wrote, for everyone.

Removes your own comment from its thread; the thread and other people's comments stay. There is no trash for comments, so it cannot be brought back.

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>",
      "comment_id": "<comment_id>"
    },
    "name": "delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYesBoard ID from list_boards, or the board URL.
comment_idYescomment_id from get_board (include_comments) or add_comment.

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 destructiveHint=true and non-idempotent, so permanence is partly given. The description adds specifics the annotations cannot: the containing thread and other comments survive, and there is no trash/undo path for comments. It does not mention permission requirements or the response, but the important behavioral traits are covered.

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?

Three short sentences, front-loaded with the action and audience, then the blast radius, then the irreversibility. No filler or restated name.

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 2-required-param destructive tool with full schema coverage and annotations carrying the safety profile, nothing an agent needs to call it correctly is 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?

Both parameters are fully documented in the schema (100% coverage) with provenance hints (list_boards, get_board with include_comments, add_comment). The description adds no parameter-level meaning, so the baseline 3 applies.

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 (delete a comment) plus the two scoping facts an agent needs: it must be your own comment, and the removal is visible to everyone. That distinguishes it from edit_comment and add_comment without naming them.

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?

'Delete a comment you wrote' implicitly states the precondition and excludes deleting other people's comments, which is a genuine when-not constraint. It does not explicitly route to edit_comment when the user actually wants to change rather than remove text, so it falls short of full alternative 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