Skip to main content
Glama

get_related_pages

Read-only

Get a page's knowledge-graph neighborhood in one compact call: its parent, child pages, outgoing links (pages its body references via inline @-links or child blocks), backlinks (pages whose bodies reference it), and — for database rows — sibling rows in the same database. Titles and IDs only, no page bodies, so it costs a fraction of re-reading pages; follow up with get_page on the neighbors that matter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYesPage ID — a standalone page, database, or database row (same IDs get_page accepts)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesThe subject page
parentYesSidebar parent (for a row, its database); null at root
childrenYesNested under this page
siblingsYesSame-database rows — database_row subjects only, null otherwise
backlinksYesPages referencing this page (parent excluded)
outgoingLinksYesPages this page's body references (children excluded)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • changedOutput schema / properties / backlinks / description
      Previous value: -"Pages whose bodies reference this page (the parent is excluded)"New value: +"Pages referencing this page (parent excluded)"
    • changedOutput schema / properties / backlinks / items / properties / databaseId / description
      Previous value: -"databases.id, present for database entries (pass to query_database / get_database_schema)"New value: +"Present for databases — pass to query_database"
    • removedOutput schema / properties / backlinks / items / properties / id / description
      Removed value: -"Item ID (pass to get_page, or query_database for databases)"
    • changedOutput schema / properties / backlinks / items / properties / linkKind / description
      Previous value: -"How the reference was made: page_link (inline @-mention) | child_block (embedded/linked block)"New value: +"page_link | child_block"
    • removedOutput schema / properties / backlinks / items / properties / title / description
      Removed value: -"Item title"
    • changedOutput schema / properties / children / description
      Previous value: -"Items nested under this page in the sidebar tree"New value: +"Nested under this page"
    • changedOutput schema / properties / children / items / properties / databaseId / description
      Previous value: -"databases.id, present for database entries (pass to query_database / get_database_schema)"New value: +"Present for databases — pass to query_database"
    • removedOutput schema / properties / children / items / properties / id / description
      Removed value: -"Item ID (pass to get_page, or query_database for databases)"
    • changedOutput schema / properties / children / items / properties / linkKind / description
      Previous value: -"How the reference was made: page_link (inline @-mention) | child_block (embedded/linked block)"New value: +"page_link | child_block"
    • removedOutput schema / properties / children / items / properties / title / description
      Removed value: -"Item title"
    • changedOutput schema / properties / outgoingLinks / description
      Previous value: -"Pages this page's body references (children already listed above are excluded)"New value: +"Pages this page's body references (children excluded)"
    • changedOutput schema / properties / outgoingLinks / items / properties / databaseId / description
      Previous value: -"databases.id, present for database entries (pass to query_database / get_database_schema)"New value: +"Present for databases — pass to query_database"
    • removedOutput schema / properties / outgoingLinks / items / properties / id / description
      Removed value: -"Item ID (pass to get_page, or query_database for databases)"
    • changedOutput schema / properties / outgoingLinks / items / properties / linkKind / description
      Previous value: -"How the reference was made: page_link (inline @-mention) | child_block (embedded/linked block)"New value: +"page_link | child_block"
    • removedOutput schema / properties / outgoingLinks / items / properties / title / description
      Removed value: -"Item title"
    • changedOutput schema / properties / page / description
      Previous value: -"The page whose neighborhood this is"New value: +"The subject page"
    • removedOutput schema / properties / page / properties / id / description
      Removed value: -"Subject page ID"
    • removedOutput schema / properties / page / properties / title / description
      Removed value: -"Subject page title"
    • changedOutput schema / properties / parent / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "databaseId": {
      -        "description": "databases.id, present for database entries (pass to query_database / get_database_schema)",
      -        "type": "string"
      -      },
      -      "id": {
      -        "description": "Item ID (pass to get_page, or query_database for databases)",
      -        "type": "string"
      -      },
      -      "linkKind": {
      -        "description": "How the reference was made: page_link (inline @-mention) | child_block (embedded/linked block)",
      -        "type": "string"
      -      },
      -      "title": {
      -        "description": "Item title",
      -        "type": "string"
      -      },
      -      "type": {
      -        "description": "page | database | database_row",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "id",
      -      "title",
      -      "type"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "databaseId": {
      +        "description": "Present for databases — pass to query_database",
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "linkKind": {
      +        "description": "page_link | child_block",
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "page | database | database_row",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "title",
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / parent / description
      Previous value: -"Parent item (for a database row, the database it belongs to); null at workspace root"New value: +"Sidebar parent (for a row, its database); null at root"
    • changedOutput schema / properties / siblings / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "items": {
      -        "description": "First few sibling rows (up to 10)",
      -        "items": {
      -          "additionalProperties": false,
      -          "properties": {
      -            "id": {
      -              "description": "Sibling row ID",
      -              "type": "string"
      -            },
      -            "title": {
      -              "description": "Sibling row title",
      -              "type": "string"
      -            }
      -          },
      -          "required": [
      -            "id",
      -            "title"
      -          ],
      -          "type": "object"
      -        },
      -        "type": "array"
      -      },
      -      "total": {
      -        "description": "Total number of other rows in the same database",
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "total",
      -      "items"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "items": {
      +        "description": "Up to 10",
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "id": {
      +              "type": "string"
      +            },
      +            "title": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "id",
      +            "title"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "total": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "total",
      +      "items"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / siblings / description
      Previous value: -"Same-database sibling rows — only for database_row subjects, null otherwise"New value: +"Same-database rows — database_row subjects only, null otherwise"
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by stating it costs a fraction of re-reading pages and returns only titles and IDs. It also covers database row behavior. No contradictions.

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?

Two sentences, no wasted words, front-loaded with the core purpose. Every sentence adds essential information.

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?

For a tool returning multiple relationship types, the description covers the main components. The output schema handles return values. Minor omission: no mention of pagination or limits, but the description is sufficiently complete for typical use.

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?

The single parameter pageId is fully described in the schema with 100% coverage. The description adds context that it accepts the same IDs as get_page (standalone page, database, or database row), enhancing understanding beyond the schema.

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 tool gets a page's knowledge-graph neighborhood in one call, listing specific components (parent, child pages, outgoing links, backlinks, sibling rows). It distinguishes from sibling tools like get_page by noting it returns only titles and IDs, not bodies.

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

Usage Guidelines5/5

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

The description explicitly advises using this tool for efficient exploration and suggests following up with get_page for details, providing clear when-to-use and when-not-to-use guidance.

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.