Markdown by mdedit.ai

Accept a review suggestion

accept_suggestion

DestructiveIdempotent

Atomically apply an existing review suggestion to the document and mark it accepted. Content changes can update an existing live public link or enabled publication sync. Use the exact suggestionId and targetId returned by add_suggestion or list_review_threads.

Input Schema

TableJSON Schema

Name	Required	Description
`context`	Yes	Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.
`targetId`	No
`articleId`	No	Internal document identifier when already available. Omit it when the user referred to the document by title.
`commandId`	Yes	Globally unique UUID for this logical review mutation. Generate it once and reuse the exact value if the tool call is retried.
`workspaceId`	No	Optional workspace ID to narrow document lookup. Omit when the document title or ID uniquely identifies a document across authorized workspaces.
`articleTitle`	No	Human-visible document title. Prefer this over asking the user for an internal document identifier.
`suggestionId`	Yes
`workspaceName`	No	Optional workspace name to narrow document lookup. A unique document title can be used without a workspace choice.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`events`	Yes
`applied`	Yes
`articleId`	Yes
`commandId`	Yes
`workspaceId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 10, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.",
+  "type": "string"
+}

changedInput schema / properties / workspaceId / description

Previous value: -"Internal workspace identifier when already available. Omit it when the user referred to a workspace by name or has only one workspace."New value: +"Optional workspace ID to narrow document lookup. Omit when the document title or ID uniquely identifies a document across authorized workspaces."

changedInput schema / properties / workspaceName / description

Previous value: -"Human-visible workspace name. Prefer this over asking the user for an internal workspace identifier."New value: +"Optional workspace name to narrow document lookup. A unique document title can be used without a workspace choice."

changedInput schema / required

Previous value: -[
-  "suggestionId",
-  "commandId"
-]New value: +[
+  "suggestionId",
+  "commandId",
+  "context"
+]

Changed5 schema fields changedSep 15, 2026

addedInput schema / properties / commandId / description

Added value: +"Globally unique UUID for this logical review mutation. Generate it once and reuse the exact value if the tool call is retried."

addedInput schema / properties / commandId / format
```
Added value: +"uuid"
```
removedInput schema / properties / commandId / minLength
```
Removed value: -1
```

addedInput schema / properties / commandId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

changedInput schema / required

Previous value: -[
-  "suggestionId"
-]New value: +[
+  "suggestionId",
+  "commandId"
+]

First observedAug 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes beyond the annotations (destructiveHint=true, idempotentHint=true) by naming the concrete downstream effects: content changes may update an existing live public link or an enabled publication sync. That is real second-order impact disclosure an agent needs before mutating a published document. It does not, however, spell out what happens to the review thread or whether the action is reversible.

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 sentences, zero filler: effect first, side effects second, invocation prerequisite third. All information is front-loaded and each sentence earns its place.

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 destructive mutation with rich annotations and an output schema (so return values need no explanation), the description covers the effect, side effects, and ID sourcing. Minor gaps remain around permissions, thread state after acceptance, and idempotency/retry semantics, though the latter are partially covered by commandId's schema text.

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?

With 75% schema coverage the baseline is 3, but the description adds provenance the schema cannot: it identifies suggestionId and targetId as values returned by add_suggestion or list_review_threads and stresses using the exact values. It says nothing about commandId, context, or the lookup-narrowing params, which the schema itself documents well.

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+resource ('apply an existing review suggestion to the document and mark it accepted') with the atomicity guarantee front-loaded. The add/reject/accept family of siblings is trivially distinguishable by the verb alone.

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?

Explicitly tells the agent to use the exact suggestionId and targetId returned by add_suggestion or list_review_threads, establishing the prerequisite and the source of the identifiers. It stops short of stating when NOT to use it (e.g. rejected/stale suggestions or the alternative reject_suggestion path).

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

All Markdown by mdedit.ai 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.

Resources

Need Help?