Skip to main content
Glama
elmapicms

elmapicms-mcp-server

Official
by elmapicms

Get Entry

get_entry

Retrieve a specific content entry from a collection using its UUID. Specify the collection slug and optionally a locale.

Instructions

Get a single content entry by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_slugYesThe collection slug
uuidYesThe entry UUID
localeNoLocale code

Implementation Reference

  • The handler function for the 'get_entry' tool. It extracts collection_slug, uuid, and optional locale from the input, builds query parameters, makes a GET request to /{collection_slug}/{uuid}, and returns the result as JSON text.
    }, async ({ collection_slug, uuid, locale }) => {
      const params: Record<string, string> = {};
      if (locale) params.locale = locale;
    
      const result = await client.get(`/${collection_slug}/${uuid}`, params);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    });
  • The input schema for 'get_entry' using Zod: requires collection_slug (string) and uuid (string), with optional locale (string).
    inputSchema: {
      collection_slug: z.string().describe("The collection slug"),
      uuid: z.string().describe("The entry UUID"),
      locale: z.string().optional().describe("Locale code"),
    },
  • The full registration block for 'get_entry' using server.registerTool(), including title, description, input schema, and handler callback.
    // ── get_entry ─────────────────────────────────────────────────────
    server.registerTool("get_entry", {
      title: "Get Entry",
      description: "Get a single content entry by UUID",
      inputSchema: {
        collection_slug: z.string().describe("The collection slug"),
        uuid: z.string().describe("The entry UUID"),
        locale: z.string().optional().describe("Locale code"),
      },
    }, async ({ collection_slug, uuid, locale }) => {
      const params: Record<string, string> = {};
      if (locale) params.locale = locale;
    
      const result = await client.get(`/${collection_slug}/${uuid}`, params);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    });
  • src/index.ts:38-38 (registration)
    The entry point that calls registerContentTools(server, client), which registers all content tools including 'get_entry'.
    registerContentTools(server, client);
  • The ElmapiClient.get() method used by the handler to make the HTTP GET request to the API endpoint.
    async get(
      path: string,
      params?: Record<string, unknown>
    ): Promise<unknown> {
      const url = new URL(`${this.baseUrl}${path}`);
      if (params) {
        const flatPairs = this.flattenParams(params);
        for (const [key, value] of flatPairs) {
          url.searchParams.append(key, value);
        }
      }
    
      const response = await fetch(url.toString(), {
        method: "GET",
        headers: this.headers(),
      });
    
      return this.handleResponse(response);
    }
Behavior2/5

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

No annotations are provided, and the description only states the basic action. It does not disclose behavior on missing entries, permissions required, or response format. For a simple read, this is minimally adequate but lacks depth.

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 sentence with no unnecessary words. It is concise but could be slightly improved by front-loading the UUID essentiality.

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?

The tool has 3 parameters, no output schema, and no annotations. The description does not explain return format, error conditions, or edge cases, making it incomplete for a holistic understanding.

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 coverage is 100% with descriptions for all parameters (collection_slug, uuid, locale). The description adds no additional parameter meaning beyond the schema, achieving the baseline 3.

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 'Get a single content entry by UUID' clearly identifies the verb (Get), resource (single content entry), and identifier (UUID). It distinguishes from sibling tools like list_entries (plural) and get_asset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like get_asset or list_entries. The implied usage is for fetching a single entry by UUID, but no when-not or context is 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/elmapicms/elmapicms-mcp-server'

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