Skip to main content
Glama

update_entry

Modifies specified fields on an existing Strapi entry as a draft, supporting collection and single types; use publish after to make changes live.

Instructions

Update an existing entry's fields. For collection types, provide the document_id. For single types (Home Page, Global, etc.), omit document_id. Pass only the fields you want to change as a JSON string. Note: updates are saved as drafts — use publish_entry afterward to make changes live.

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": "update_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesJSON string with fields to update
localeNoLocale code
document_idNoDocument ID (required for collection types)
content_typeYesContent type UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the most consequential non-obvious behavior: updates are saved as drafts and are not live until publish_entry runs. It also implies partial-update semantics ("pass only the fields you want to change") rather than a full replace. It stops short of covering permissions, failure modes for an invalid document_id, or what the response contains.

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 the action, then the parameter rule, then the critical draft-state caveat. No filler or redundancy; each sentence carries information an agent needs before calling.

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 mutation tool with no annotations and no output schema, the description covers the essentials: partial-update semantics, the conditional document_id rule, and the non-obvious draft state with its required follow-up call. Remaining gaps around auth requirements, error behavior, and return shape are relatively minor given the tool's straightforward contract.

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%, so the baseline is 3, and the description largely restates the schema's own note that document_id applies to collection types. It does add genuine meaning for data by clarifying that only the fields to change should be sent, implying patch-style partial update rather than wholesale replacement, but locale is left entirely to 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 opens with a specific verb+resource ("Update an existing entry's fields") and immediately scopes it against the create/publish siblings by saying the entry already exists and that publish_entry is a separate later step. The collection-vs-single-type distinction further pins down what this tool operates on, so an agent can identify it without opening the 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?

It gives concrete usage conditions: supply document_id for collection types, omit it for single types like Home Page or Global, and call publish_entry afterward to make changes live. It names the follow-up alternative explicitly but doesn't state when to prefer create_entry over this tool or any exclusion conditions.

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