Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_update_comment

Destructive

Replaces the text of one Notion comment. Notion's API edits only comments created through the same connection, and answers not found for any other. Returns the comment.

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": {
      "comment_id": "<comment_id>",
      "text": "<text>"
    },
    "name": "notion-mcp__notion_update_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe new text, as plain text. Over 2,000 characters is split into several text pieces.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
comment_idYesThe comment's id, from notion_get_comments or notion_create_comment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds context the annotations do not: the connection-scoped edit restriction, the not-found failure mode for foreign comments, and the fact that the updated comment is returned. It does not discuss permission scopes or reversibility beyond what destructiveHint implies.

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?

Two short sentences, with the operation front-loaded and the constraint plus return value following. Every clause carries information an agent needs; nothing is padded.

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 three-parameter mutation with full schema coverage and annotations covering safety, the description supplies the one non-obvious runtime constraint and notes the return value despite there being no output schema. Minor omission: it does not say whether the previous text is recoverable, though destructiveHint signals that it is not.

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%, with text, account, and comment_id all documented in the schema itself, including the 2,000-character split behavior and where comment_id comes from. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 opens with a specific verb and resource, 'Replaces the text of one Notion comment,' which is distinguishable from notion_create_comment, notion_delete_comment, and notion_get_comments without opening any schema. It does not explicitly name those siblings, but the verb alone disambiguates the operation.

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

Usage Guidelines3/5

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

The description states an important precondition, namely that only comments created through the same connection can be edited and anything else returns not found; this is genuine when-it-works guidance. It gives no explicit advice on choosing this tool over notion_create_comment or notion_update_page_content, so usage is only implied.

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

All DataToRAG 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