Skip to main content
Glama
Sign In
esa MCP Server

esa MCP Server

Official
by esaio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get comments for a specific post

esa_get_post_comments
Read-only

Retrieves a paginated list of comments for a specific esa.io post, enabling you to review or process discussion threads page by page.

Instructions

Retrieves a list of comments for a specific post with pagination support.

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

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 comments 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without description help. The description adds 'pagination support', which is useful beyond annotations, but omits sort order, defaults, and the fact that teamName is required (the schema covers that last point).

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?

A single compact sentence with the resource and scope front-loaded and no wasted words. It is appropriately sized for a simple read tool, though the pagination clause is slightly gratuitous given the schema already documents page/perPage.

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

Completeness3/5

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

Annotations cover the read-only safety profile and the schema fully documents all parameters, so the description needn't carry much. Still, it omits result ordering and the required-teamName workflow nuance that would help an agent call it correctly on the first try.

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%, so all four parameters are already documented, including the teamName prerequisite pointing to esa_get_teams. The description adds only a generic mention of pagination and no syntax or default details beyond the schema, so baseline 3 is appropriate.

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?

Uses a specific verb ('Retrieves') and resource ('list of comments') scoped to 'a specific post', which distinguishes it from the team-wide esa_get_team_comments and single-comment esa_get_comment. It doesn't name those siblings explicitly, but the scope is unambiguous.

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?

The phrase 'for a specific post' implies the per-post use case versus team-wide listing, but no explicit when-to-use or when-not-to-use guidance is given. An agent must infer the alternative from sibling names.

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