Skip to main content
Glama

create_entry

Create a new content entry in Contentful by providing the content type ID, localized field values (with locale keys), space ID, and environment ID.

Instructions

Create a new entry in Contentful. Before executing this function, you need to know the contentTypeId (not the content type NAME) and the fields of that contentType. You can get the fields definition by using the GET_CONTENT_TYPE tool. IMPORTANT: All field values MUST include a locale key (e.g., 'en-US') for each value, like: { title: { 'en-US': 'My Title' } }. Every field in Contentful requires a locale even for single-language content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentTypeIdYesThe ID of the content type for the new entry
fieldsYesThe fields of the entry with localized values. Example: { title: { 'en-US': 'My Title' }, description: { 'en-US': 'My Description' } }
spaceIdYesThe ID of the Contentful space. This must be the space's ID, not its name, ask for this ID if it's unclear.
environmentIdYesThe ID of the environment within the space, by default this will be called Mastermaster
Behavior4/5

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

With no annotations, the description covers the critical locale behavior and the need for content type knowledge. However, it does not disclose potential side effects (e.g., whether the entry is automatically published) or error conditions, leaving some behavioral gaps.

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 concise yet comprehensive, with each sentence contributing necessary information. It is front-loaded with the main purpose and logically structured with prerequisites and key instructions.

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?

Despite lacking an output schema and annotations, the description covers prerequisites, locale format, and parameter semantics well. It is slightly incomplete regarding the return value or confirmation of creation, which may be inferred but not explicitly stated.

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

Parameters5/5

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

All parameters have schema descriptions, and the tool description adds valuable clarifications: contentTypeId must be the ID not name, and fields require locale keys with a concrete example. This significantly enhances understanding beyond the schema.

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 clearly states 'Create a new entry in Contentful', providing a specific verb and resource. It includes unique details like the locale requirement, distinguishing it from update and publish operations among siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the prerequisite (knowing contentTypeId and fields) and directs the agent to the GET_CONTENT_TYPE tool for field definitions. Also emphasizes the locale requirement, guiding correct invocation.

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/ivo-toby/contentful-mcp'

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