NomaCMS MCP Server

Official

by NomaCMS

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Bulk Update Asset Metadata

bulk_update_asset_metadata

Atomically update metadata for multiple assets by UUID, with automatic rollback if any update fails.

Instructions

Update metadata for multiple assets atomically by UUID. If one item fails, all updates are 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": {
      "items": "<items>"
    },
    "name": "bulk_update_asset_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	Array of metadata updates

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Discloses key behavioral trait: atomicity with rollback on failure. No annotations provided, so description adds significant value. Lacks details on permissions or rate limits, but atomicity is well covered.

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?

Two efficient sentences: first states purpose and resource, second adds behavioral detail. No wasted words.

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?

Tool is simple (one parameter, array of objects). Atomicity and rollback are covered. No output schema, but a brief mention of expected return could improve completeness; otherwise well-specified.

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?

Input schema has 100% description coverage, so baseline is 3. Description adds 'atomically' and 'by UUID' but does not add parameter-specific details beyond what schema provides.

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 it updates metadata for multiple assets atomically by UUID. Distinguishes from siblings like 'update_asset' (single) and 'bulk_update_entries' (different resource).

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?

Atomicity is mentioned, suggesting use when all-or-nothing updates are needed. However, no explicit exclusions or alternative tools (e.g., 'use update_asset for single updates') are provided.

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