Skip to main content
Glama
Sign In
esa MCP Server

esa MCP Server

Official
by esaio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get backlinks for a specific post

esa_get_post_backlinks
Read-only

Retrieve a paginated list of posts that link back to a specified post, excluding archived and WIP posts and ordering results by newest backlink registration.

Instructions

Retrieves a paginated list of posts that reference (link back to) the specified post. Archived posts and WIP posts are excluded. Results are ordered by backlink registration date (newest references first).

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": {
      "postNumber": "<postNumber>"
    },
    "name": "esa_get_post_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (starts from 1)
perPageNoNumber of items per page
teamNameNoTeam name (required). Use esa_get_teams first to see available teams.
postNumberYesThe post number to get backlinks for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.13.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/non-destructive, so the description's added value is the filtering rule (archived and WIP posts excluded) and the ordering guarantee (newest reference first) plus pagination — meaningful disclosure an agent cannot get from annotations alone.

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?

Three short sentences, front-loaded with what is returned, then exclusions, then ordering. No filler and nothing redundant.

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 still conveys result type (list of referencing posts), filtering, and sort order, which is enough to call and interpret it. The item shape is not described, but that is a minor gap for a read-only list tool.

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 each parameter is documented there, so baseline 3 applies. The description adds nothing about the pagination parameters or the fact that teamName is effectively required, so it does not exceed 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?

States a specific verb and resource ('Retrieves a paginated list of posts that reference...the specified post') and disambiguates the direction of the relation, which matters next to siblings like esa_get_post and esa_get_post_comments.

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?

Use case is implied by the name and description, but there is no explicit statement of when to choose this over related tools (e.g. esa_get_post_comments for discussion vs backlinks for references). The prerequisite of resolving a team name via esa_get_teams appears only in the schema, not the description.

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