MCP: content_create/content_update ignores taxonomies field (categories/tags not assigned) #1760
Closed
khoinguyenpham04
announced in
Roadmap
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
This Roadmap discussion mirrors #953: MCP: content_create/content_update ignores taxonomies field (categories/tags not assigned).
Use this discussion to upvote the roadmap item and discuss priority, use cases, and product feedback. Keep implementation tracking, reproduction details, and PR-specific feedback on the source issue.
roadmap/1.0,roadmap/api-mcp-agentsOriginal Issue
Problem
content_createandcontent_updateMCP tools accept ataxonomiesfield without error, but do not persist taxonomy assignments (categories, tags) to the content item. The field is silently ignored.This is a follow-up to #621, which was closed after SEO and bylines support was added to
content_update. The taxonomy part of that issue was not resolved.Steps to reproduce
Verified via
content_get- the returned item has notaxonomiesfield at all.Expected behavior
content_createandcontent_updateshould persist taxonomy assignments, either by term slug or term ID.Workaround
The REST API endpoint works correctly:
This is undocumented but functional. I used it to bulk-assign categories and tags to 15 posts.
Additionally,
content_getdoes not return taxonomy assignments in its response - you need to useGET /_emdash/api/content/posts/{postId}/terms/{taxonomyName}to check.Environment
content_create,content_update,taxonomy_list_termstoolsAll reactions