Skip to main content
Glama
Sign In
esa MCP Server

esa MCP Server

Official
by esaio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a new comment on a post

esa_create_comment

Creates a new Markdown comment on an existing esa.io post in a specified team, using the post number and comment body.

Instructions

Creates a new comment on an existing post in an esa team.

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>",
      "bodyMd": "<bodyMd>"
    },
    "name": "esa_create_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoComment author's screen_name (owner permission required)
bodyMdYesThe comment content in Markdown format. Use 4 spaces for indentation.
teamNameNoTeam name (required). Use esa_get_teams first to see available teams.
postNumberYesThe post number to comment on

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description adds the precondition that the post must exist, but says nothing about permission requirements for authoring as another user (only the param schema mentions owner permission) or what gets returned.

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 front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification rather than deliberate economy.

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?

For a four-parameter mutation tool with no output schema, the definition leans entirely on fully documented params and safety annotations. What remains missing is authorization behavior and a hint about the created comment's return shape, which an agent would want before writing.

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 description coverage is 100%, so all four parameters — user, bodyMd, teamName, postNumber — are already documented with constraints and defaults. The description adds no format, syntax, or validation detail beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource: creating a comment on an existing post, with the esa-team scope named. This clearly separates it from esa_create_post and esa_update_comment, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus esa_create_post, esa_update_comment, or esa_get_post_comments. The only implied condition is that the target post must already exist, which is inferred from 'existing post' rather than stated as a rule.

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