Skip to main content
Glama
Sign In
notion-mpm

notion-mpm

by bobmatnyc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_comments

Retrieve all comments on a Notion page or block to review discussions and feedback.

Instructions

Retrieve all comments on a Notion page or block.

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": {
      "block_id": "<block_id>"
    },
    "name": "get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idYesPage or block UUID to retrieve comments for
page_sizeNoMaximum number of comments to return
start_cursorNoPagination cursor from a previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It implies a read-only operation but does not mention pagination behavior, rate limits, or authentication requirements. The claim to retrieve 'all' comments is misleading given the page_size and start_cursor parameters, which indicate paginated results.

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 a single, concise sentence with no wasted words. It is appropriately front-loaded and easy to parse.

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

Completeness3/5

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

Given the tool's low complexity and complete schema, the description suffices for basic understanding but omits return format and pagination behavior. For a list-returning tool without an output schema, the lack of return value details leaves a gap.

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?

The schema provides full descriptions for all three parameters, including block_id, page_size, and start_cursor with 100% coverage. The description adds no additional parameter semantics beyond what the schema already specifies.

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 'Retrieve all comments on a Notion page or block' uses a specific verb and resource, clearly distinguishing this from sibling tools like create_comment or get_page. It clearly states the operation and target.

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

Usage Guidelines3/5

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

The description provides no explicit guidance on when to use this tool versus alternatives, such as create_comment for writing or get_block for block details. The intended usage is implied by the name and simple description, but there is no mention of pagination or exclusions.

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

Deploy Server

Other Tools