Skip to main content
Glama

update_entry

Update specific fields of a Contentful entry without overwriting others. Provide only the fields and locales to change, each value with a locale key. Merges with existing data.

Instructions

Update an existing entry. The handler will merge your field updates with the existing entry fields, so you only need to provide the fields and locales you want to change. IMPORTANT: All field values MUST include a locale key (e.g., 'en-US') for each value, like: { title: { 'en-US': 'My Updated Title' } }. Every field in Contentful requires a locale even for single-language content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryIdYes
fieldsYesThe fields to update with localized values. Example: { title: { 'en-US': 'My Updated Title' } }
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?

No annotations exist, so the description carries full burden. It discloses the merge behavior (non-destructive partial update) and emphasizes the locale key requirement, adding critical behavioral context beyond the schema.

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?

Three sentences front-load the purpose, then merge behavior, then a critical warning with example. No fluff, every sentence earns its place.

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?

Covers the key nuance (locale requirement) and merge behavior. Lacks description of return value or error conditions, but given moderate complexity and no output schema, it provides sufficient context for an agent to use the tool correctly.

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 has 75% coverage; the description adds value by detailing the locale structure for field values, reinforcing and extending the schema's localized example, which is essential for correct usage.

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 'Update an existing entry,' specifying the verb and resource. It distinguishes from siblings like create_entry, delete_entry, and get_entry by focusing on modification.

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?

The description explains merge behavior ('you only need to provide the fields...you want to change'), implying partial updates. However, it does not explicitly mention when not to use or compare to alternatives, leaving guidance implicit.

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