Skip to main content
Glama
NomaCMS

NomaCMS MCP Server

Official
by NomaCMS

Create Field

create_field

Add a field to a collection by specifying its type, label, and name. Supports text, rich text, relations, and group fields with validation rules.

Instructions

Add a new field to a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesField identifier in kebab-case (max 60 chars)
typeYesField type: text, number, richtext, boolean, date, media, relation, select, longtext, group, etc.
labelYesDisplay label (max 60 chars)
optionsNoField-specific options (e.g. { repeatable: true } for group fields). For richtext: { editor: { type: 1, outputFormat: 'html' | 'markdown' } }. For relation: { relation: { collection: <target collection id, slug, or name>, type: 1 | 2 }, includeDraft?: boolean } (1 = one-to-one, 2 = one-to-many).
descriptionNoField description
placeholderNoPlaceholder text
validationsNoValidation rules (e.g. { required: { status: true, message: 'Required' } })
collection_slugYesThe slug of the collection to add the field to
parent_field_idNoInternal ID of a group field to nest this field under
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as error handling, side effects (e.g., constraint validation), or return value. The term 'Add' suggests mutation but lacks detail.

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 with no extraneous words. Efficient and to the point.

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?

For a complex tool with 9 parameters and no output schema, a one-sentence description is insufficient. It lacks context on behavior, error conditions, and return format, leaving the agent underinformed.

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 coverage is 100% and descriptions are present, so the schema already documents parameters. The description adds no additional semantic value beyond the schema, meeting the baseline.

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 'Add a new field to a collection' clearly states the verb (add) and resource (field to collection), distinguishing it from siblings like update_field or reorder_fields.

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?

No explicit when-to-use or alternatives are provided, but the context of creating versus updating or reordering fields is implied. Missing prerequisites like collection existence or field uniqueness.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NomaCMS/nomacms-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server