Skip to main content
Glama
esa MCP Server

esa MCP Server

Official
by esaio

Get a specific esa post

esa_get_post
Read-only

Retrieves a specific esa team post by post number and reports its backlink count, so you can inspect the post and see how many articles reference it.

Instructions

Retrieves a specific post from an esa team by post number. The response always includes backlinks_count (the number of posts referencing this one). To list the referencing posts themselves, use esa_get_post_backlinks. To fetch comments, use esa_get_post_comments.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNameNoTeam name (required). Use esa_get_teams first to see available teams.
truncateNoWhether to truncate body_md to avoid overwhelming the agent context (default: true). If the response ends with '... (truncated)' and you need the full body (e.g. before calling esa_update_post to preserve the tail), retry with truncate: false. body_md_stats reports the full body's character and line counts even when truncated.
postNumberYesThe post number to retrieve

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.4/5.0
Behavior4/5

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

Annotations already establish this is a safe, non-destructive read, so the description doesn't need to re-state safety. It adds non-obvious behavioral context the annotations can't carry: the response always contains backlinks_count, which is a guaranteed output field. It says nothing about body truncation behavior, though the schema handles that in detail.

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 the core action, then the returned field, then the routing alternatives. No filler and no restating of the title.

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?

A simple read-only getter with full annotation coverage and a rich schema; the description supplies the one output detail (backlinks_count) not captured elsewhere. Without an output schema, one could wish for a brief note on other fields returned, but the essential call-correctness information is present.

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 schema-driven descriptions for teamName, truncate, and postNumber are already detailed (defaults, truncation fallback, team lookup guidance). The description adds only 'by post number', which the schema already covers; baseline 3 applies.

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+resource ('Retrieves a specific post ... by post number') and draws an explicit boundary against the nearest siblings, esa_get_post_backlinks and esa_get_post_comments. An agent can pick this tool over any sibling without opening a schema.

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?

Names two alternatives explicitly and states the condition that selects each ('To list the referencing posts themselves...', 'To fetch comments...'). It also implies the natural read path (look up by post number) and defers team discovery to esa_get_teams via the schema.

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