Notion MCP Server

Create Comment

notion_create_comment

Add a comment to a Notion page or reply in an existing discussion thread. Provide rich text content and specify either a page ID or discussion ID.

Instructions

Create a comment in Notion. This requires the integration to have 'insert comment' capabilities. You can either specify a page parent or a discussion_id, but not both.

Input Schema

TableJSON Schema

Name	Required	Description
`format`	No	Specify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.
`parent`	No	Parent object that specifies the page to comment on. Must include a page_id if used.
`rich_text`	Yes	Array of rich text objects representing the comment content.
`discussion_id`	No	The ID of an existing discussion thread to add a comment to.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv2.0.0May 18, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +{}
```
- removedInput schema / properties / format / default
```
Removed value: -"markdown"
```
- addedInput schema / properties / parent / additionalProperties
```
Added value: +{}
```
- changedInput schema / properties / parent / properties / page_id / description
```
Previous value: -"The ID of the page to comment on.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."New value: +"The ID of the page to comment on. It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."
```
- addedInput schema / properties / rich_text / items / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / rich_text / items / properties / annotations / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / rich_text / items / properties / equation / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / rich_text / items / properties / mention / additionalProperties
```
Added value: +{}
```
- removedInput schema / properties / rich_text / items / properties / mention / oneOf
```
Removed value: -[
-  {
-    "required": [
-      "database"
-    ]
-  },
-  {
-    "required": [
-      "date"
-    ]
-  },
-  {
-    "required": [
-      "link_preview"
-    ]
-  },
-  {
-    "required": [
-      "page"
-    ]
-  },
-  {
-    "required": [
-      "template_mention"
-    ]
-  },
-  {
-    "required": [
-      "user"
-    ]
-  }
-]
```
- addedInput schema / properties / rich_text / items / properties / mention / properties / database / additionalProperties
```
Added value: +{}
```
- changedInput schema / properties / rich_text / items / properties / mention / properties / database / properties / id / description
```
Previous value: -"The ID of the mentioned database.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."New value: +"The ID of the mentioned database. It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."
```
- addedInput schema / properties / rich_text / items / properties / mention / properties / date / additionalProperties
```
Added value: +{}
```
- removedInput schema / properties / rich_text / items / properties / mention / properties / date / properties / end / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- removedInput schema / properties / rich_text / items / properties / mention / properties / date / properties / time_zone / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedInput schema / properties / rich_text / items / properties / mention / properties / link_preview / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / rich_text / items / properties / mention / properties / page / additionalProperties
```
Added value: +{}
```
- changedInput schema / properties / rich_text / items / properties / mention / properties / page / properties / id / description
```
Previous value: -"The ID of the mentioned page.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."New value: +"The ID of the mentioned page. It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."
```
- addedInput schema / properties / rich_text / items / properties / mention / properties / template_mention / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / rich_text / items / properties / mention / properties / user / additionalProperties
```
Added value: +{}
```
- changedInput schema / properties / rich_text / items / properties / mention / properties / user / properties / id / description
```
Previous value: -"The ID of the user.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."New value: +"The ID of the user. It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-)."
```
- addedInput schema / properties / rich_text / items / properties / text / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / rich_text / items / properties / text / properties / link / additionalProperties
```
Added value: +{}
```
AddedSep 17, 2025

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false, signaling a write operation. The description adds value by specifying the requirement for 'insert comment' capabilities and the constraint of not providing both parent and discussion_id. This goes beyond 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, with the purpose and key requirement in the first sentence and a critical constraint in the second. Every sentence earns its place, and it is front-loaded with the verb and resource.

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?

Given the complexity of the rich_text parameter, the schema covers it thoroughly. The description lacks mention of return values or error handling, but for a creation tool with no output schema, it provides sufficient context for an agent 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 description coverage is 100%, so the schema already documents each parameter. However, the description adds crucial semantic information about the mutual exclusivity of parent and discussion_id, which is not explicitly stated in the schema. This compensates beyond the baseline 3.

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 clearly states the action ('Create a comment') and the resource ('in Notion'). It distinguishes from siblings by specifying the unique operation, as there is no other create comment tool. The mention of two target options (page or discussion_id) adds specificity.

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?

The description provides clear context for parameter selection by stating that either parent or discussion_id can be used, but not both. While it does not explicitly mention alternatives like notion_retrieve_comments for reading, the mutual exclusivity guidance is helpful for correct invocation.

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

Create Comment

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools