Skip to main content
Glama
esaio

esa MCP Server

Official
by esaio

Create a new esa post

esa_create_post
Destructive

Create a new post in an esa team, optionally adding tags, category, and marking as work in progress.

Instructions

Creates a new post in an esa team with optional tags, category, and WIP status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wipNoWhether the post is Work In Progress. Set to false to ship it (mark as complete and ready to be published)
nameYesThe 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.
Behavior3/5

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

Annotations declare destructiveHint: true, which is consistent. The description adds minimal extra context (WIP status) but does not cover side effects, permissions, or team scope. With annotations handling the safety profile, a 3 is appropriate.

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?

A single, front-loaded sentence with no wasted words. Every word is informative and the structure is optimal for quick scanning.

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

Completeness2/5

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

For a tool with 7 parameters and no output schema, the description lacks prerequisites (e.g., teamName requirement), post-creation state defaults, and error conditions. It is too sparse for an AI agent to fully understand the invocation context.

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 baseline is 3. The description lists parameters generically but adds no meaning beyond the schema's own parameter descriptions. It does not explain interactions or default behavior.

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?

The description uses a specific verb ('creates') and resource ('post'), and lists key optional attributes (tags, category, WIP status). It clearly distinguishes from sibling tools like esa_update_post or esa_append_post.

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?

No guidance on when to use this tool versus alternatives. Siblings like esa_update_post or esa_ship_post exist for different lifecycle stages, but no exclusion criteria or preferred contexts are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/esaio/esa-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server