Skip to main content
Glama

delete_entry

Removes a specific entry from the content management system by specifying its UID and content type UID. Simplifies data cleanup and management in contentstack-mcp.

Instructions

Deletes an entry identified by its UID and content type UID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_type_uidYesContent type UID
entry_uidYesEntry UID to delete

Implementation Reference

  • The handler function that executes the tool logic: sends a DELETE request to the Contentstack API to delete the specified entry and returns success/error messages.
    async ({ content_type_uid, entry_uid }) => {
      try {
        const response = await axios.delete(`${API_BASE_URL}/content_types/${content_type_uid}/entries/${entry_uid}`, {
          headers: getHeaders(),
        })
    
        return {
          content: [
            {
              type: 'text',
              text: `Entry "${entry_uid}" deleted successfully from content type "${content_type_uid}".`,
            },
          ],
        }
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: handleError(error as ApiError),
            },
          ],
          isError: true,
        }
      }
    },
  • Zod input schema defining the parameters: content_type_uid (string) and entry_uid (string).
    {
      content_type_uid: z.string().describe('Content type UID'),
      entry_uid: z.string().describe('Entry UID to delete'),
    },
  • src/index.ts:662-695 (registration)
    The server.tool call that registers the 'delete_entry' tool with name, description, input schema, and handler function.
    server.tool(
      'delete_entry',
      'Deletes an entry identified by its UID and content type UID.',
      {
        content_type_uid: z.string().describe('Content type UID'),
        entry_uid: z.string().describe('Entry UID to delete'),
      },
      async ({ content_type_uid, entry_uid }) => {
        try {
          const response = await axios.delete(`${API_BASE_URL}/content_types/${content_type_uid}/entries/${entry_uid}`, {
            headers: getHeaders(),
          })
    
          return {
            content: [
              {
                type: 'text',
                text: `Entry "${entry_uid}" deleted successfully from content type "${content_type_uid}".`,
              },
            ],
          }
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: handleError(error as ApiError),
              },
            ],
            isError: true,
          }
        }
      },
    )
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral context. It states the destructive action ('Deletes') but doesn't cover critical aspects like permissions required, whether deletion is permanent/reversible, error conditions, or side effects. This is inadequate for a mutation tool with zero 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 with zero wasted words. It's front-loaded with the core action and directly states the required identifiers.

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?

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks essential context about permissions, consequences, error handling, and how it relates to sibling operations (e.g., whether deletion affects published status). The 100% schema coverage doesn't compensate for these behavioral gaps.

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%, with both parameters clearly documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., no format examples, validation rules, or relationship between the two UIDs). Baseline 3 is appropriate when 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 action ('Deletes') and the resource ('an entry'), specifying it's identified by UID and content type UID. It distinguishes from siblings like 'delete_content_type' by focusing on entries, but doesn't explicitly differentiate from other entry-related tools like 'unpublish_entry' or 'update_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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., entry must exist), exclusions (e.g., cannot delete published entries), or relationships with siblings like 'unpublish_entry' or 'delete_content_type'.

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

Related 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/darekrossman/contentstack-mcp'

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