Skip to main content
Glama

esa_create_post

Create new posts in esa with titles, markdown content, tags, and categories to organize team documentation.

Instructions

Create a new post

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPost title
body_mdNoPost body (Markdown format)
tagsNoList of tags for the post
categoryNoPost category
wipNoWhether to mark as WIP (Work In Progress)
messageNoChange message
userNoPoster's screen_name (only team owners can specify)
template_post_idNoID of the post to use as a template

Implementation Reference

  • Handler for the 'esa_create_post' tool in the CallToolRequest switch statement. Validates input and calls esaClient.createPost to execute the tool.
    case "esa_create_post": {
      const args = request.params.arguments as unknown as CreatePostArgs;
      if (!args.name) {
        throw new Error("name is required");
      }
      const response = await esaClient.createPost(args);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool definition including name, description, and input schema for 'esa_create_post'.
    const createPostTool: Tool = {
      name: "esa_create_post",
      description: "Create a new post",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Post title",
          },
          body_md: {
            type: "string",
            description: "Post body (Markdown format)",
          },
          tags: {
            type: "array",
            items: { type: "string" },
            description: "List of tags for the post",
          },
          category: {
            type: "string",
            description: "Post category",
          },
          wip: {
            type: "boolean",
            description: "Whether to mark as WIP (Work In Progress)",
            default: true,
          },
          message: {
            type: "string",
            description: "Change message",
          },
          user: {
            type: "string",
            description: "Poster's screen_name (only team owners can specify)",
          },
          template_post_id: {
            type: "number",
            description: "ID of the post to use as a template",
          },
        },
        required: ["name"],
      },
    };
  • index.ts:607-619 (registration)
    Registration of 'esa_create_post' tool (via createPostTool) in the ListToolsRequest handler's tools array.
        tools: [
          listPostsTool,
          getPostTool,
          createPostTool,
          updatePostTool,
          listCommentsTool,
          getCommentTool,
          createCommentTool,
          getMembersTool,
          getMemberTool,
        ],
      };
    });
  • EsaClient method that performs the HTTP POST request to create a new post on the Esa API.
    async createPost(postData: Omit<CreatePostArgs, 'template_post_id'> & { template_post_id?: number }): Promise<any> {
      const url = `${this.baseUrl}/posts`;
      const response = await fetch(url, {
        method: "POST",
        headers: this.headers,
        body: JSON.stringify({ post: postData }),
      });
    
      return response.json();
    }
  • TypeScript interface defining the arguments for createPost, used for type validation in the handler.
    interface CreatePostArgs {
      name: string;
      body_md?: string;
      tags?: string[];
      category?: string;
      wip?: boolean;
      message?: string;
      user?: string;
      template_post_id?: number;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new post' implies a write operation, but it doesn't disclose critical traits like required permissions, whether the post is publicly visible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is extremely concise ('Create a new post')—just three words—and front-loaded with the core action. There is zero wasted language, and every word earns its place by directly conveying the tool's purpose without redundancy.

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 (a mutation tool with 8 parameters) and no annotations or output schema, the description is incomplete. It lacks information on behavioral traits, usage context, and output expectations. While the schema covers parameters well, the description doesn't compensate for the missing behavioral and contextual details needed for safe and effective use.

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 the schema fully documents all 8 parameters with clear descriptions (e.g., 'Post title', 'Post body (Markdown format)'). The description adds no additional parameter semantics beyond what's in the schema. According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

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 'Create a new post' clearly states the verb ('Create') and resource ('post'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'esa_update_post' (which modifies existing posts) and 'esa_list_posts' (which retrieves posts). However, it doesn't specify what type of post or platform, which could be inferred from context but isn't explicit.

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. It doesn't mention prerequisites (e.g., authentication), when not to use it (e.g., for updating existing posts), or direct alternatives like 'esa_update_post' for modifications. The agent must infer usage from the tool name and sibling list alone.

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

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