Skip to main content
Glama

list-comments

Retrieve comments from Notion pages or blocks to track discussions and feedback within your workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idNoThe ID of the page to get comments from
block_idNoThe ID of the block to get comments from
start_cursorNoPagination cursor
page_sizeNoNumber of results to return (max 100)

Implementation Reference

  • MCP tool handler for 'list-comments': calls NotionService.listComments, handles pagination and errors, returns JSON-formatted results.
    async ({ page_id, block_id, start_cursor, page_size }) => {
      try {
        if (!page_id && !block_id) {
          return {
            content: [
              {
                type: "text",
                text: "Error: Either page_id or block_id must be provided",
              },
            ],
            isError: true,
          };
        }
    
        const result = await this.notionService.listComments({
          page_id,
          block_id,
          start_cursor,
          page_size,
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error("Error in list-comments tool:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error: Failed to list comments - ${
                (error as Error).message
              }`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema defining parameters for the list-comments tool: page_id or block_id (optional), pagination options.
    {
      page_id: z
        .string()
        .optional()
        .describe("The ID of the page to get comments from"),
      block_id: z
        .string()
        .optional()
        .describe("The ID of the block to get comments from"),
      start_cursor: z.string().optional().describe("Pagination cursor"),
      page_size: z
        .number()
        .min(1)
        .max(100)
        .optional()
        .describe("Number of results to return (max 100)"),
    },
  • Registration of the 'list-comments' tool on the MCP server within registerCommentTools().
    this.server.tool(
      "list-comments",
      {
        page_id: z
          .string()
          .optional()
          .describe("The ID of the page to get comments from"),
        block_id: z
          .string()
          .optional()
          .describe("The ID of the block to get comments from"),
        start_cursor: z.string().optional().describe("Pagination cursor"),
        page_size: z
          .number()
          .min(1)
          .max(100)
          .optional()
          .describe("Number of results to return (max 100)"),
      },
      async ({ page_id, block_id, start_cursor, page_size }) => {
        try {
          if (!page_id && !block_id) {
            return {
              content: [
                {
                  type: "text",
                  text: "Error: Either page_id or block_id must be provided",
                },
              ],
              isError: true,
            };
          }
    
          const result = await this.notionService.listComments({
            page_id,
            block_id,
            start_cursor,
            page_size,
          });
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          console.error("Error in list-comments tool:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error: Failed to list comments - ${
                  (error as Error).message
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • NotionService.listComments: core logic maps page_id/block_id to block_id and calls Notion SDK client.comments.list with pagination.
    async listComments(params: CommentQuery) {
      try {
        if (!params.page_id && !params.block_id) {
          throw new NotionAPIError(
            "Either page_id or block_id must be provided",
            "INVALID_REQUEST_PARAMETERS"
          );
        }
    
        // According to the Notion API docs, we should use block_id for both pages and blocks
        // Pages are technically blocks in Notion's data model
        const blockId = params.block_id || params.page_id;
    
        return await this.client.comments.list({
          block_id: blockId!, // Non-null assertion since we've checked above
          start_cursor: params.start_cursor,
          page_size: params.page_size,
        });
      } catch (error) {
        this.handleError(error);
      }
    }
  • TypeScript type and Zod schema for CommentQuery parameters used in NotionService.listComments.
    export const CommentQuerySchema = z.object({
      block_id: z.string().optional(),
      page_id: z.string().optional(),
      start_cursor: z.string().optional(),
      page_size: z.number().min(1).max(100).optional(),
    });
    
    export type CommentQuery = z.infer<typeof CommentQuerySchema>;
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