Niches · CMS & website publishing
Change content that is already on the site
Two or three companies' docs show a full fit.
What counts as done
Only the requested field or item changes, every other field, locale, block and list row is byte-identical after the write, the editor UI still opens the entry normally, and a stale read is refused rather than overwriting someone else's change.
How agents ask for it: our prices have gone up, change them on the services page
, take Dave off the committee page
, fix the typo on the about page
, update the footer address
Does the job 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| DatoCMS BB Dato Srl | Updates leave omitted fields untouched, blocks are edited by id, and meta.current_version makes a stale write fail with 422 STALE_ITEM_VERSION. source |
| Ghost C Ghost Foundation Ltd | Reads return the stored Lexical JSON by default, and PUT requires updated_at for collision detection, so a stale write is refused; tags and authors are replaced only if sent. source |
Does the job, with a limit 15
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| BCMS F Becomes tech, LLC | update-entries changes one language's meta and content, but the docs show no version or updated-at check, so a stale write is not refused. source |
| ButterCMS D ButterCMS LLC | Page PATCH and PUT are partial and per locale, but repeaters must be resent whole and no version or updated-at check refuses a stale write. source |
| Contentstack B Contentstack Inc. | update_an_entry is a PUT that replaces the locale's field data; no patch operation or version precondition is in the tool definition, so a stale read overwrites. source |
| Cosmic BB Cosmic Inc. | PATCH updates named metadata keys and leaves others, but no version or modified-at precondition is documented, so a stale write is not refused. source |
| Directus C Monospace Inc. (doing business as Directus) | update takes partial data and relational deltas with create, update and delete per row id, but no version or If-Match check refuses a stale write. source |
| dotCMS C dotCMS LLC | PATCH on the default fire route merges fields before firing an action, but no stale-write check was found in the workflow reference. source |
| Hygraph B Hygraph GmbH | update_entry sets only the fields sent and relations take connect and disconnect per item, but no version precondition is documented, so a stale write isn't refused. source |
| Kontent.ai BB Kontent CZ s.r.o. | update-content-item-variant leaves omitted elements untouched, but rich text with components must be resent whole, and no version precondition refuses a stale write. source |
| Payload D Payload CMS, Inc. | Updates send only changed fields, but acc-19 shows the MCP plugin stripping array row ids so a one-locale write deletes other locales' subfields, and no stale-write check is documented. source |
| Prismic C Prismic.io Inc. | update_document branches a new version from a base version but takes the document's full content, so every slice must be resent; whether a changed base is refused isn't documented. source |
| Sanity BB Sanity US Inc. (with Sanity AS) | patch_documents sets one path and insert addresses array items, edits land in the draft, but no revision precondition appears in the MCP or patch docs read, so a stale write isn't refused. source |
| Storyblok B Storyblok GmbH | Any Management API write is reachable, but the pages read show no patch operation or version precondition, so a change means resending the story's content object. source |
| Strapi BB Strapi, Inc. | update_<slug> works, but acc-15 shows it replacing a whole dynamic zone, deleting rows another editor added since the read while reporting isError false. source |
| Webflow BB Webflow, Inc. | update_collection_items edits items by id as drafts, but no version precondition refuses a stale write, and acc-24 shows API-inserted rich-text images vanishing in the Designer. source |
| WordPress B WordPress.org, an open-source project. The WordPress trademark belongs to the WordPress Foundation | context=edit returns raw block markup for a safe write-back, but acc-12 shows an MCP server reading rendered HTML and storing it without blocks, and core has no stale-write check. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| CookieYes MCP Server D CookieYes Limited | Cannot edit site content. Banner text is read-only and legal copy changes are blocked, per the tool table. source |
What stops agents finishing
- update tool replaces whole lists, deleting concurrent additions, and reports success
- read returns rendered HTML so a write back destroys block structure
- schema validation rejects edits on documents the native editor saves
Around it
Before: cms.find-entry. After: cms.publish-and-verify.
Where this comes from
Weight 13 of 100 in CMS & website publishing: 7 of 39 accounts, several of them data-loss bugs found in 2026 (Strapi, Payload, WordPress block markup)
The same as data: /api/v1/use-cases/cms.edit-in-place.json, or the MCP tool get_use_case with id cms.edit-in-place. Other jobs in this category: /api/v1/niches?category=cms.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.