Skip to main content
Glama
elmapicms

elmapicms-mcp-server

Official
by elmapicms

Delete Entry

delete_entry

Soft-deletes a content entry by moving it to the trash, from which it can be restored via the admin panel.

Instructions

Soft-delete a content entry (moves to trash). Can be restored from the admin panel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_slugYesThe collection slug
uuidYesThe entry UUID

Implementation Reference

  • The async callback that executes the delete_entry tool logic: calls client.delete() with the collection slug and entry UUID, then returns the result.
    }, async ({ collection_slug, uuid }) => {
      const result = await client.delete(`/${collection_slug}/${uuid}`);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    });
  • Zod input schema for delete_entry defining 'collection_slug' and 'uuid' as required string parameters.
    inputSchema: {
      collection_slug: z.string().describe("The collection slug"),
      uuid: z.string().describe("The entry UUID"),
    },
  • Registration of the 'delete_entry' tool via server.registerTool, with title 'Delete Entry' and description explaining it's a soft-delete (moves to trash).
    server.registerTool("delete_entry", {
      title: "Delete Entry",
      description:
        "Soft-delete a content entry (moves to trash). Can be restored from the admin panel.",
      inputSchema: {
        collection_slug: z.string().describe("The collection slug"),
        uuid: z.string().describe("The entry UUID"),
      },
    }, async ({ collection_slug, uuid }) => {
      const result = await client.delete(`/${collection_slug}/${uuid}`);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    });
  • The ElmapiClient.delete() method that performs the actual HTTP DELETE request to the API, used by the delete_entry tool.
    async delete(path: string, body?: unknown): Promise<unknown> {
      const response = await fetch(`${this.baseUrl}${path}`, {
        method: "DELETE",
        headers: this.headers(),
        body: body ? JSON.stringify(body) : undefined,
      });
    
      return this.handleResponse(response);
    }
Behavior3/5

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

No annotations provided; description carries full burden. It discloses the soft-delete behavior and restore possibility, but lacks details on permissions, reversal window, or side effects. Adequate but not thorough.

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?

Single sentence, no fluff, directly conveys the essential behavioral nuance (soft-delete, restorable). Efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation with two well-described parameters and no output schema, the description covers the key behavioral aspects. Could mention return value, but not critical.

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?

Input schema has 100% coverage with descriptions for both parameters. The tool description adds no additional parameter context beyond what schema provides. Baseline score of 3 is appropriate.

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?

Description clearly states the action (soft-delete), the resource (content entry), and the consequence (moves to trash, restorable). It distinguishes from sibling 'delete_asset' by specifying 'entry'.

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 explicit guidance on when to use this tool versus alternatives like 'update_entry' or 'delete_asset'. The soft-delete nature is mentioned but not framed as a usage condition.

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