Skip to main content
Glama
Sign In
esa MCP Server

esa MCP Server

Official
by esaio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Archive a post

esa_archive_post
Destructive

Move a post to the Archived category, preserving its path as Archived/ (e.g., dev/docs becomes Archived/dev/docs).

Instructions

Archives a post by moving it to the Archived/ category. If the post is in 'dev/docs', it becomes 'Archived/dev/docs'. Posts without category go to 'Archived'.

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

Input Schema

NameRequiredDescriptionDefault
messageNoChange message for the archive
teamNameNoTeam name (required). Use esa_get_teams first to see available teams.
postNumberYesThe post number to archive

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.14.1
    • changedInput schema / properties / message / description
      Previous value: -"Archive message for the post"New value: +"Change message for the archive"
  3. 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 destructiveHint=true and readOnlyHint=false, and the description goes beyond them by disclosing the exact post-state after the call: category becomes 'Archived/<old category>' or 'Archived' if uncategorized. It does not say whether the original category is preserved for later restoration, whether missing Archived categories are auto-created, or who can call it.

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?

Two sentences, with the core effect front-loaded and the conditional category rule immediately after. Nothing is redundant or padded.

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?

For a 3-parameter mutation with full schema coverage and no output schema, the description covers the essential 'what happens to the post' question. The remaining gap - reversibility and whether the resulting category is created automatically - is minor but would matter for a destructiveHint=true 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 description coverage is 100% (postNumber, teamName with a pointer to esa_get_teams, and message), so the schema carries parameter semantics. The description adds no per-parameter detail such as what message is used for or whether teamName is required in practice.

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 (archive) and resource (post) plus the mechanism: moving to the Archived/ category, preserving the existing category path, and falling back to 'Archived' when none exists. No sibling tool archives a post, and the visible outcome distinguishes it cleanly from esa_update_post or esa_delete_comment.

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 use case is implied by the name and description (retire a post without deleting it), but there is no explicit 'use this when / use X instead' guidance, and no mention of the alternative of recategorizing via esa_update_post. Prerequisites (teamName) live 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