Skip to main content
Glama

create-comment

Add comments to Notion pages to provide feedback, ask questions, or create threaded discussions within your workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe ID of the page to comment on
textYesThe comment text content
discussion_idNoOptional discussion ID for threaded comments

Implementation Reference

  • The main handler function for the MCP 'create-comment' tool. Formats user inputs into Notion API payload and delegates to notionService.createComment, handling response and errors appropriately.
    async ({ page_id, text, discussion_id }) => {
      try {
        const result = await this.notionService.createComment({
          parent: {
            page_id: page_id,
          },
          rich_text: [
            {
              type: "text",
              text: {
                content: text,
              },
            },
          ],
          discussion_id,
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error("Error in create-comment tool:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error: Failed to create comment - ${
                (error as Error).message
              }`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema (Zod) for the 'create-comment' tool, validating page_id, text, and optional discussion_id.
    {
      page_id: z.string().describe("The ID of the page to comment on"),
      text: z.string().describe("The comment text content"),
      discussion_id: z
        .string()
        .optional()
        .describe("Optional discussion ID for threaded comments"),
    },
  • Registers the 'create-comment' tool with the MCP server inside the registerCommentTools method, providing name, input schema, and handler.
    this.server.tool(
      "create-comment",
      {
        page_id: z.string().describe("The ID of the page to comment on"),
        text: z.string().describe("The comment text content"),
        discussion_id: z
          .string()
          .optional()
          .describe("Optional discussion ID for threaded comments"),
      },
      async ({ page_id, text, discussion_id }) => {
        try {
          const result = await this.notionService.createComment({
            parent: {
              page_id: page_id,
            },
            rich_text: [
              {
                type: "text",
                text: {
                  content: text,
                },
              },
            ],
            discussion_id,
          });
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          console.error("Error in create-comment tool:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error: Failed to create comment - ${
                  (error as Error).message
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper method in NotionService that performs the actual Notion API call to create a comment using the SDK client.
    async createComment(params: CreateComment) {
      try {
        return await this.client.comments.create(params);
      } catch (error) {
        this.handleError(error);
      }
    }
  • Detailed Zod schema and TypeScript type for Notion's CreateComment API parameters, used internally by the handler.
    export const CreateCommentSchema = z.object({
      parent: z.object({
        page_id: z.string(),
      }),
      rich_text: z.array(
        z.object({
          type: z.literal("text"),
          text: z.object({
            content: z.string(),
            link: z
              .object({
                url: z.string(),
              })
              .optional(),
          }),
          annotations: z
            .object({
              bold: z.boolean().optional(),
              italic: z.boolean().optional(),
              strikethrough: z.boolean().optional(),
              underline: z.boolean().optional(),
              code: z.boolean().optional(),
              color: z
                .enum([
                  "default",
                  "gray",
                  "brown",
                  "orange",
                  "yellow",
                  "green",
                  "blue",
                  "purple",
                  "pink",
                  "red",
                ])
                .optional(),
            })
            .optional(),
        })
      ),
      discussion_id: z.string().optional(),
    });
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ramidecodes/mcp-server-notion'

If you have feedback or need assistance with the MCP directory API, please join our Discord server