Skip to main content
Glama
d-kimuson

ESA MCP Server

by d-kimuson

read_esa_multiple_posts

Retrieve multiple posts from esa.io using specified post numbers to access content efficiently.

Instructions

Read multiple posts in esa.io.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNameNomy-team
postNumbersYes

Implementation Reference

  • Core handler logic for reading multiple ESA posts by parallel API calls to fetch each post and excluding body_html.
    async readPosts(teamName: string, postNumbers: readonly number[]) {
      return await Promise.all(
        postNumbers.map(async (postNumber) => {
          const response = await this.callApi(() =>
            getV1TeamsTeamNamePostsPostNumber(
              teamName,
              postNumber,
              {},
              {
                headers: {
                  Authorization: `Bearer ${this.apiKey}`,
                },
              }
            )
          )
          const { body_html, ...others } = response.data
          return others
        })
      )
    }
  • src/server.ts:122-133 (registration)
    MCP tool registration including name, description, input schema, and thin handler delegating to ApiClient.readPosts via formatTool.
    server.tool(
      "read_esa_multiple_posts",
      "Read multiple posts in esa.io.",
      {
        teamName: z.string().default(getRequiredEnv("DEFAULT_ESA_TEAM")),
        postNumbers: z.array(z.number()),
      },
      async (input) =>
        await formatTool(
          async () => await client.readPosts(input.teamName, input.postNumbers)
        )
    )
  • Zod input schema for the tool: teamName (with default) and array of post numbers.
    {
      teamName: z.string().default(getRequiredEnv("DEFAULT_ESA_TEAM")),
      postNumbers: z.array(z.number()),
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a safe read operation, requires permissions, has rate limits, returns paginated results, or handles errors. 'Read' implies non-destructive, but this isn't explicitly confirmed, leaving gaps 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 with one sentence, front-loaded and zero waste. It directly states the tool's purpose without unnecessary words, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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 2 parameters with 0% schema coverage, no annotations, no output schema, and sibling tools, the description is incomplete. It doesn't cover parameter meanings, usage context, return values, or behavioral traits, making it inadequate for an agent to reliably invoke this tool without additional inference or trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'teamName' or 'postNumbers' represent, their formats, or constraints (e.g., teamName default 'my-team', postNumbers as array of numbers). The description fails to provide meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Read multiple posts in esa.io' clearly states the verb ('Read') and resource ('multiple posts'), but it's vague about scope and doesn't differentiate from sibling tools like 'read_esa_post' (singular) or 'search_esa_posts'. It specifies 'multiple' but lacks details about what constitutes 'multiple' versus other read operations.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites like authentication, compare to 'read_esa_post' for single posts or 'search_esa_posts' for filtered queries, or specify use cases like batch retrieval. The agent must infer usage from the name 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/d-kimuson/esa-mcp-server'

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