tela

by zcag

Overview Schema Source Related Servers Discussions Admin

Remote

List backlinks

list_backlinks

Read-only

List incoming wikilinks to a page to see what depends on it before editing or deleting, or to explore the link graph.

Instructions

List the pages that link TO the given page via [[wikilink]] / tela://page/{id} — its incoming references (read-only). Use to see what depends on a page before you edit or delete it, or to walk the explicit link graph; for semantically similar pages that don't link it, use related_pages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page_id`	Yes	page whose incoming links to list

Output Schema

TableJSON Schema

Name	Required	Description	Default
`backlinks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only and non-destructive. The description adds value by detailing the link types checked and that it shows incoming references, which is helpful beyond the annotations.

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 concise sentences: the first defines the tool's exact behavior, the second provides usage context. No wasted words, front-loaded with key information.

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

Completeness5/5

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

The description fully covers purpose, usage, and link types for a simple tool with one parameter. Output schema exists, so return values need no elaboration. Complete for the given context.

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% and the single parameter 'page_id' is self-explanatory. The description does not add new parameter semantics beyond what the schema provides, matching the baseline.

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 lists incoming references via specific link types ([[wikilink]] or tela://page/{id}), and explicitly distinguishes it from the sibling tool 'related_pages' which handles semantically similar non-linking pages.

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?

Provides explicit guidance on when to use (to see dependencies before edit/delete, or walk link graph) and when not to (for semantically similar pages, use related_pages), including a named alternative.

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