Skip to main content
Glama

mcp-notion__notion-list-page-backlinks

Read-onlyIdempotent

List the pages that link to or mention a Notion page (backlinks), in the same workspace. Returns IDs, titles and URLs only; fetch a result to read it. Only pages you can open are listed. Follow next_cursor for more. 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": {
      "page_id": "<page_id>"
    },
    "name": "mcp-notion__notion-list-page-backlinks"
  }
}

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.
typesNoOnly return these kinds of backlinks. page_mention is an inline @-mention in text, a title, or a caption; link_to_page is a link-to-page block; property_mention is a mention in a database property; comment_mention is a mention in a comment. Omit for all kinds.
cursorNonext_cursor from the previous call.
page_idYesID or URL of the page or database to find backlinks for.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
page_sizeNoMaximum backlinks to return (1-100; default 25).
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is structured data. The description does add genuinely useful behavior: the restricted result shape, the permission scoping ('Only pages you can open are listed'), and pagination via next_cursor. The final sentence about Royally merely restates the read-only annotation and adds little beyond that, though it is not contradictory.

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 purpose is front-loaded and the following sentences each add a distinct fact: return shape, follow-up action, permission scope, pagination. The closing line about Royally marking it read-only is the weakest sentence, restating an annotation already provided, but it costs only one clause.

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?

With no output schema, the description takes on the job of describing returns and does so concisely (IDs, titles, URLs). Pagination, permission filtering and the follow-up fetch path are all covered. Minor gaps remain around ordering or what a backlink object looks like, but nothing an agent needs to call it is missing.

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 coverage is 100%, with every parameter documented including enum meanings for `types` and a cursor definition, so the schema carries the load and a 3 baseline applies. The description adds only that next_cursor is used for further pages, which is already implied by the schema's cursor description.

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?

The description opens with a specific verb and resource ('List the pages that link to or mention a Notion page') and glosses the term as 'backlinks', so the operation is unambiguous. It also states scope ('in the same workspace'). It doesn't name a sibling alternative, but no sibling in the list appears to do the same thing, so differentiation is implicit rather than earned.

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?

It gives real routing guidance: 'Returns IDs, titles and URLs only; fetch a result to read it' tells the agent to follow up with the fetch tool rather than expecting content here. 'Follow next_cursor for more' explains the continuation pattern. It stops short of explicit when-not-to-use conditions (e.g. searching by content).

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