Skip to main content
Glama
d-kimuson

ESA MCP Server

by d-kimuson

update_esa_post

Modify existing esa.io posts by updating content, metadata, or status using the ESA MCP Server's API integration.

Instructions

Update an existing post in esa.io. Required parameters: postNumber. Optional parameters: name, body_md, tags, category, wip, message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNameNomy-team
postNumberYes
nameNo
body_mdNo
tagsNo
categoryNo
wipNo
messageNo

Implementation Reference

  • Handler function that processes the input for update_esa_post, calls the ApiClient.updatePost method, and returns a formatted response object.
    async (input) =>
      await formatTool(async () => {
        const { teamName, postNumber, ...updateData } = input
        return client
          .updatePost(teamName, postNumber, updateData)
          .then((data) => ({
            success: true,
            number: data.number,
            full_name: data.full_name,
            url: data.url,
            wip: data.wip,
            created_at: data.created_at,
            updated_at: data.updated_at,
            message: data.message,
            kind: data.kind,
            tags: data.tags,
            category: data.category,
            revision_number: data.revision_number,
            created_by: data.created_by,
            updated_by: data.updated_by,
          }))
      })
  • Zod schema for validating the input parameters of the update_esa_post tool.
    {
      teamName: z.string().default(getRequiredEnv("DEFAULT_ESA_TEAM")),
      postNumber: z.number(),
      name: z.string().optional(),
      body_md: z.string().optional(),
      tags: z.array(z.string()).optional(),
      category: z.string().optional(),
      wip: z.boolean().optional(),
      message: z.string().optional(),
    },
  • src/server.ts:167-202 (registration)
    MCP server.tool registration for the update_esa_post tool, including description, input schema, and handler.
    server.tool(
      "update_esa_post",
      "Update an existing post in esa.io. Required parameters: postNumber. Optional parameters: name, body_md, tags, category, wip, message.",
      {
        teamName: z.string().default(getRequiredEnv("DEFAULT_ESA_TEAM")),
        postNumber: z.number(),
        name: z.string().optional(),
        body_md: z.string().optional(),
        tags: z.array(z.string()).optional(),
        category: z.string().optional(),
        wip: z.boolean().optional(),
        message: z.string().optional(),
      },
      async (input) =>
        await formatTool(async () => {
          const { teamName, postNumber, ...updateData } = input
          return client
            .updatePost(teamName, postNumber, updateData)
            .then((data) => ({
              success: true,
              number: data.number,
              full_name: data.full_name,
              url: data.url,
              wip: data.wip,
              created_at: data.created_at,
              updated_at: data.updated_at,
              message: data.message,
              kind: data.kind,
              tags: data.tags,
              category: data.category,
              revision_number: data.revision_number,
              created_by: data.created_by,
              updated_by: data.updated_by,
            }))
        })
    )
  • Helper method in ApiClient class that handles the actual API call to update an ESA post using the generated ESA API client.
    async updatePost(
      teamName: string,
      postNumber: number,
      post: Partial<PostInput>
    ) {
      return this.callApi(() =>
        patchV1TeamsTeamNamePostsPostNumber(
          teamName,
          postNumber,
          { post },
          {
            headers: {
              Authorization: `Bearer ${this.apiKey}`,
            },
          }
        )
      ).then((response) => response.data)
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('Update') but lacks details on permissions, side effects, error handling, or response format. This is inadequate for a tool that modifies data without structured safety hints.

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?

The description is a single, efficient sentence that front-loads the purpose and lists parameters concisely. There's no wasted text, though it could be slightly more structured by separating usage guidance from parameter details.

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?

Given the complexity of an update operation with 8 parameters, no annotations, and no output schema, the description is incomplete. It fails to cover behavioral aspects like authentication needs, rate limits, or what the tool returns, making it insufficient for safe and effective use by an AI agent.

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?

The description lists all parameters as 'Required' or 'Optional', which adds some semantics beyond the schema's 0% description coverage. However, it doesn't explain what each parameter means (e.g., 'wip' or 'body_md'), leaving significant gaps in understanding despite compensating partially for the low schema coverage.

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?

The description clearly states the action ('Update') and resource ('an existing post in esa.io'), making the purpose evident. However, it doesn't explicitly differentiate this tool from its sibling 'create_esa_post' beyond the verb, missing a direct comparison that would elevate it to a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'create_esa_post' or 'delete_esa_post', nor does it mention prerequisites such as needing an existing post. It only lists parameters without contextual usage advice.

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/d-kimuson/esa-mcp-server'

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