Skip to main content
Glama

esa_get_post

Retrieve detailed information about a specific post from the esa platform using its post number, including optional related data like comments or stargazers.

Instructions

Get detailed information about a specific post

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_numberYesPost number to retrieve
includeNoRelated data to include in the response (e.g. 'comments,stargazers')

Implementation Reference

  • Executes the esa_get_post tool: validates post_number, calls EsaClient.getPost, returns JSON response.
    case "esa_get_post": {
      const args = request.params.arguments as unknown as GetPostArgs;
      if (!args.post_number) {
        throw new Error("post_number is required");
      }
      const response = await esaClient.getPost(args.post_number, args.include);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Defines Tool metadata, name, description, and input schema for esa_get_post.
    const getPostTool: Tool = {
      name: "esa_get_post",
      description: "Get detailed information about a specific post",
      inputSchema: {
        type: "object",
        properties: {
          post_number: {
            type: "number",
            description: "Post number to retrieve",
          },
          include: {
            type: "string",
            description: "Related data to include in the response (e.g. 'comments,stargazers')",
          },
        },
        required: ["post_number"],
      },
    };
  • Core implementation: constructs URL and fetches post data from Esa API.
    async getPost(post_number: number, include?: string): Promise<any> {
      const params = new URLSearchParams();
      
      if (include) params.append("include", include);
    
      const url = `${this.baseUrl}/posts/${post_number}${params.toString() ? `?${params}` : ""}`;
      const response = await fetch(url, { headers: this.headers });
    
      return response.json();
    }
  • index.ts:607-618 (registration)
    Registers getPostTool (esa_get_post) in the list of tools provided to MCP clients.
      tools: [
        listPostsTool,
        getPostTool,
        createPostTool,
        updatePostTool,
        listCommentsTool,
        getCommentTool,
        createCommentTool,
        getMembersTool,
        getMemberTool,
      ],
    };
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. It states the tool retrieves detailed information, implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, error handling, or what 'detailed information' includes. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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 a read operation with two parameters and no annotations or output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, response format), usage context relative to siblings, and doesn't compensate for the absence of an output schema, leaving the agent uncertain about what to expect.

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 already documents both parameters ('post_number' and 'include') thoroughly. The description adds no additional meaning beyond what the schema provides, such as examples of 'include' values or context for post numbers. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific post'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'esa_get_comment' or 'esa_list_posts', which would require mentioning it retrieves a single post by identifier rather than listing or fetching comments.

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 siblings like 'esa_list_posts' for listing posts or 'esa_get_comment' for comments, nor does it specify prerequisites such as needing a post number. This leaves the agent without context for tool selection.

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