Skip to main content
Glama

create_entry

Creates a new entry in a Strapi collection type using field values supplied as a JSON string. Call describe_content_type first to confirm exact field names.

Instructions

Create a new entry in a collection type (e.g. a new News Article or Product). Pass field values as a JSON string in the 'data' parameter. Use describe_content_type first to know the exact field names. Cannot be used for single types — those already exist, use update_entry instead.

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": {
      "content_type": "<content_type>",
      "data": "<data>"
    },
    "name": "create_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesJSON string with field values, e.g. {"title": "My Article", "body": "Content..."}
content_typeYesContent type UID (must be a collection type)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two real behaviors: the JSON-string encoding of field values and the hard failure mode for single types, plus the describe_content_type prerequisite. It does not say what happens on invalid field names, whether duplicate/required fields are enforced, what the call returns (e.g. the new entry's ID), or what permissions are needed.

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?

Four short sentences, front-loaded with purpose, then payload mechanics, then prerequisite, then the exclusion/alternative. No filler and no repetition; each sentence changes what the agent would do.

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?

For a 2-parameter create tool with no annotations and no output schema, the description covers the essentials: what it creates, the payload format, the discovery step, and the unsupported case. The main gap is the return value and error behavior, which the agent cannot infer from any structured field since no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: it tells the agent that 'data' must be a JSON string (not an object) and that its field names come from describe_content_type rather than from guessing. It also restates the collection-type constraint on 'content_type', reinforcing the schema's parenthetical.

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?

States a specific verb and resource ("Create a new entry"), scopes it to collection types with a concrete example ("a new News Article or Product"), and explicitly contrasts with update_entry for single types. An agent can tell this apart from update_entry and get_entry without opening any schema.

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?

Gives a concrete prerequisite workflow ("Use describe_content_type first to know the exact field names") and an exclusion rule with the named alternative ("Cannot be used for single types ... use update_entry instead"). What's missing is broader routing guidance — e.g. how to discover a content type UID before calling, or when to prefer a different creation path.

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