Skip to main content
Glama
Sign In
NomaCMS MCP Server

NomaCMS MCP Server

Official
by NomaCMS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Bulk Delete Entries

bulk_delete_entries

Atomically delete multiple content entries using their UUIDs. If one deletion fails, all deletions are rolled back to prevent partial data loss.

Instructions

Delete multiple content entries atomically by UUID. If one delete fails, no entries are deleted.

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>",
      "uuids": "<uuids>"
    },
    "name": "bulk_delete_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoIf true, permanently delete instead of soft-delete
uuidsYesEntry UUIDs to delete
collection_slugYesThe collection slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses atomicity and failure atomic behavior, but does not mention authorization requirements, return values, or the distinction between soft/hard delete (force parameter is not described).

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 sentence that is front-loaded with the action and key constraint (atomicity). Every word is essential, with no redundancy.

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?

Given the lack of annotations and output schema, the description is incomplete. It omits behavioral traits such as whether the operation is destructive, what happens on success (e.g., return values), and does not explain the force parameter's implications.

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 the schema already documents all parameters. The description adds no additional parameter semantics beyond the schema, warranting the baseline score of 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 uses a specific verb ('Delete') and resource ('multiple content entries') and highlights the atomicity ('atomically by UUID'), which clearly distinguishes it from sibling tools like delete_entry (single entry) and other bulk operations.

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?

The description explains when to use this tool (for atomic bulk deletion) and the critical behavior ('If one delete fails, no entries are deleted'). It does not explicitly mention alternatives, but the context is clear given sibling tools.

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

Deploy Server

Other Tools