NomaCMS MCP Server

Official

by NomaCMS

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Delete Entry

delete_entry

Soft-delete a content entry by moving it to trash; it can be restored from the admin panel.

Instructions

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

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": {
      "collection_slug": "<collection_slug>",
      "uuid": "<uuid>"
    },
    "name": "delete_entry"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes	The entry UUID
`collection_slug`	Yes	The collection slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Discloses soft-delete and restorability, which adds value beyond schema. However, lacks details on permissions, side effects, or linked data impact. With no annotations, more depth would be beneficial.

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 wasted words, front-loaded with key action.

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?

Adequate for a simple tool with two parameters and no output schema. Covers core behavior and recovery path, but missing some potential edge cases.

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 already describes both parameters with 100% coverage; description does not add extra meaning beyond what is in schema.

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?

Clearly states the action (soft-delete), the target (content entry), and key behavior (moves to trash, restorable). Distinguishes from other delete tools like 'delete_asset' and 'bulk_delete_entries'.

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?

Implies usage for entries that need restore capability, but does not explicitly state when to use vs alternatives like 'bulk_delete_entries' or 'delete_asset'.

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