Skip to main content
Glama

delete_entry

Permanently deletes a collection-type entry from Strapi by document ID; cannot remove single-type entries, and the action cannot be undone.

Instructions

Permanently delete an entry from a collection type. Requires the document_id. Cannot delete single type entries. This action cannot be undone — confirm with the user before deleting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content_type": "<content_type>",
      "document_id": "<document_id>"
    },
    "name": "delete_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesDocument ID to delete
content_typeYesContent type UID (must be a collection type)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses permanence, irreversibility, the content-type restriction, and the required user confirmation. It does not mention auth/permission requirements or whether the entry's media/references are affected, which keeps it from a 5.

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?

Three short sentences, front-loaded with the destructive nature and constraints, with no filler. The final confirmation instruction could have been merged with the first sentence, but nothing is wasted.

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 two-parameter mutating tool with no annotations and no output schema, the description covers the essential safety and eligibility facts an agent needs. Only the post-condition (what the response contains, or what happens to dependent data) is left unaddressed.

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 both parameters are already documented in the schema, including the collection-type constraint on content_type. The description adds no syntax, format, or sourcing guidance for document_id, so the baseline 3 applies.

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?

States a specific verb and resource ('Permanently delete an entry') plus a scope restriction ('from a collection type'), which together with the delete-vs-create/update distinction in the sibling list lets an agent identify the tool without opening the schema.

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

Usage Guidelines4/5

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

Gives an explicit when-not ('Cannot delete single type entries') and a procedural precondition ('confirm with the user before deleting'), which is clear context for a destructive operation. It stops short of naming an alternative path for the excluded single-type case, so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.