Is your feature request related to a problem? Please describe.
After multiple update cycles, an audit showed that 11+ entries had fieldStatus: changed β they were in draft and not live β even though some had been through several update cycles. There was no proactive signal during the session that entries were accumulating as unpublished drafts. The user discovered the problem only at handoff.
Describe the solution you'd like
- After any update_entry, the MCP response could make the draft state explicit (e.g. βEntry saved as draft. Not published.β).
- A get_publish_status tool that lists all unpublished entries for a given page or tab would allow a sweep before handoff, rather than discovering the problem at the end.
Describe alternatives you've considered
- Manually checking each entry in the Contentful UI β tedious and error-prone.
- Relying on AI instructions to track draft status β fragile and easy to miss.
Additional context
Reported after an incident where multiple unpublished drafts were discovered at handoff.
Is your feature request related to a problem? Please describe.
After multiple update cycles, an audit showed that 11+ entries had fieldStatus: changed β they were in draft and not live β even though some had been through several update cycles. There was no proactive signal during the session that entries were accumulating as unpublished drafts. The user discovered the problem only at handoff.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Reported after an incident where multiple unpublished drafts were discovered at handoff.