Skip to main content
Glama

mcp-notion__notion-get-suggested-edit

Read-onlyIdempotent

Read the exact before-and-after diff and currently allowed actions for one pending suggested edit. Call this before deciding whether to accept or reject it.

Requires a Business or Enterprise workspace plan. Call this tool directly. If access is denied, follow the recovery guidance in the result. Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "suggested_edit_url": "<suggested_edit_url>"
    },
    "name": "mcp-notion__notion-get-suggested-edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
suggested_edit_urlYesPending suggested-edit discussion URL returned by get_comments or create_suggested_edit.
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds value beyond that: a workspace-plan prerequisite, the instruction to call it directly, and an error path ('if access is denied, follow the recovery guidance in the result'). It notes the tool runs without confirmation, which explains observable behavior not captured by the annotations.

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 operative instruction and the object of the read are front-loaded in a single sentence, followed by prerequisites and error handling in the right order. The trailing note about the server marking it read-only is somewhat meta and partly redundant with the annotations, which keeps this from a 5.

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 single-object read tool with full parameter documentation and no output schema, the description covers purpose, sequencing, plan requirement, and failure handling. The one remaining gap is that it never characterizes the response (diff format, which actions are 'allowed'), though no output schema exists to carry that.

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% and each parameter is documented in the schema, including the provenance of suggested_edit_url. The description only reinforces that the URL points at a pending edit; it adds no format, sourcing, or constraint detail beyond the schema, so the baseline 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?

States a specific verb and resource ('Read the exact before-and-after diff and currently allowed actions for one pending suggested edit'), which tells an agent exactly what comes back. It doesn't explicitly contrast with a sibling read tool, but the scope (one pending suggested edit, keyed by its discussion URL) is narrow enough to be unambiguous.

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?

'Call this before deciding whether to accept or reject it' gives a concrete sequencing rule tied to a decision point. The plan prerequisite (Business or Enterprise) is also stated. What's missing is any when-not guidance or reference to the alternative accept/reject tools an agent would move to next.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources