Skip to main content
Glama
Sign In
esa MCP Server

esa MCP Server

Official
by esaio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update an existing esa post

esa_update_post
Destructive

Update an existing esa team post by post number, including title, content, tags, category, and WIP status; set WIP to false to ship it.

Instructions

Updates an existing post in an esa team by post number. You can update the title, content, tags, category, and WIP status. To ship a post (mark as complete), set wip to false - this is preferred over using esa_ship_post when updating other fields simultaneously. To only add content to the start or end of the body, use esa_append_post or esa_prepend_post instead.

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

Input Schema

NameRequiredDescriptionDefault
wipNoWhether the post is Work In Progress. Set to false to ship it (mark as complete and ready to be published)
nameNoThe post name (title)
tagsNoTags for the post
bodyMdNoThe post content in Markdown format. Use 4 spaces for indentation.
messageNoUpdate message for the post
categoryNoCategory path (e.g., 'dev/docs')
teamNameNoTeam name (required). Use esa_get_teams first to see available teams.
postNumberYesThe post number to update
originalRevisionNoOriginal revision to check for conflicts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / originalRevision / 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?

Adds real meaning beyond the annotations: clarifies that wip=false is the shipping mechanism and that this tool supersedes esa_ship_post for combined updates, which the destructiveHint alone would not convey. The implication that content edits replace the body (rather than append) is only conveyed indirectly via the append/prepend routing, and the originalRevision conflict-check behavior is never described.

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 tight sentences with the core action first, the mutation surface second, and the alternative routing last. No filler and no repetition 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?

Covers the core operation and the sibling disambiguation well for a mutating 9-parameter tool. It omits the teamName requirement and the originalRevision conflict-check semantics, both of which matter for a tool that can overwrite post bodies, though the nested object is described in the schema.

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 nine parameters are already documented, setting the baseline at 3. The description adds genuine semantic value only for wip (false = ship/complete); the rest of the field list largely restates what the schema property descriptions already say.

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 ('Updates an existing post in an esa team by post number') and enumerates the mutation surface (title, content, tags, category, WIP). It also names the sibling tools it is not (esa_append_post, esa_prepend_post, esa_ship_post), so an agent can distinguish it without opening any 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?

Gives explicit routing rules: use this instead of esa_ship_post when shipping plus changing other fields, and use esa_append_post/esa_prepend_post when only adding to the body. Both the when and the when-not are stated with named alternatives.

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