NomaCMS MCP Server

Official

by NomaCMS

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Bulk Create Entries

bulk_create_entries

Create multiple content entries atomically, with automatic rollback if any entry fails.

Instructions

Create multiple content entries atomically. If one item fails, the whole request is rolled back.

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>",
      "items": "<items>"
    },
    "name": "bulk_create_entries"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	Array of entries to create
`collection_slug`	Yes	The collection slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions atomicity and rollback, which is key, but lacks other traits like error reporting, limits, or side effects.

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?

Single sentence covering core purpose and key behavior; concise and to the point, though could be slightly more structured.

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?

No output schema, so description should hint at return value or error handling; it only mentions rollback on failure, missing success response and error details.

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 covers 100% of parameters with detailed descriptions (e.g., items.data format), so description adds no new parameter info beyond the atomicity note, which is behavioral.

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 'Create multiple content entries atomically', which is a specific verb and resource, and distinguishes from siblings like 'create_entry' (single) and 'bulk_update_entries' (update).

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?

Description implies usage for batch creation but does not explicitly state when to use vs alternatives (e.g., single create_entry) or any prerequisites/exclusions.

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