Ghost MCP Server

ghost_update_post

Update an existing Ghost CMS post by modifying title, content, status, tags, images, or SEO fields. Only specified fields are changed, keeping others intact.

Instructions

Updates an existing post in Ghost CMS. Can update title, content, status, tags, images, and SEO fields. Only the provided fields are changed; omitted fields remain unchanged. Note: tags and authors arrays are fully replaced, not merged with existing values.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	No
`html`	No	HTML content of the post
`slug`	No
`status`	No		draft
`visibility`	No		public
`featured`	No
`feature_image`	No
`feature_image_alt`	No
`feature_image_caption`	No
`excerpt`	No
`custom_excerpt`	No
`meta_title`	No
`meta_description`	No
`og_image`	No
`og_title`	No
`og_description`	No
`twitter_image`	No
`twitter_title`	No
`twitter_description`	No
`canonical_url`	No
`tags`	No	Array of tag names or IDs to associate with the post. On update, this fully replaces the existing tags array (not merged).
`authors`	No	Array of author IDs or emails. On update, this fully replaces the existing authors array (not merged).
`published_at`	No	Scheduled publish time (ISO 8601 format)
`codeinjection_head`	No
`codeinjection_foot`	No
`custom_template`	No	Custom template filename
`email_only`	No	Whether post is email-only
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.14.3May 18, 2026
Removedv1.14.2May 9, 2026

Changed30 schema fields changedv1.12.2Apr 29, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / authors

Added value: +{
+  "description": "Array of author IDs or emails. On update, this fully replaces the existing authors array (not merged).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / canonical_url

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / codeinjection_foot
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / codeinjection_head
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / custom_excerpt

Added value: +{
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / custom_template

Added value: +{
+  "description": "Custom template filename",
+  "type": "string"
+}

addedInput schema / properties / email_only

Added value: +{
+  "default": false,
+  "description": "Whether post is email-only",
+  "type": "boolean"
+}

addedInput schema / properties / excerpt

Added value: +{
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / feature_image

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / feature_image_alt

Added value: +{
+  "maxLength": 191,
+  "type": "string"
+}

addedInput schema / properties / feature_image_caption

Added value: +{
+  "maxLength": 5000,
+  "type": "string"
+}

addedInput schema / properties / featured

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / html

Added value: +{
+  "description": "HTML content of the post",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / id

Added value: +{
+  "pattern": "^[a-f0-9]{24}$",
+  "type": "string"
+}

addedInput schema / properties / meta_description

Added value: +{
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / meta_title

Added value: +{
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / og_description

Added value: +{
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / og_image

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / og_title

Added value: +{
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / published_at

Added value: +{
+  "description": "Scheduled publish time (ISO 8601 format)",
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+  "type": "string"
+}

addedInput schema / properties / slug

Added value: +{
+  "pattern": "^[a-z0-9-]+$",
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "default": "draft",
+  "enum": [
+    "draft",
+    "published",
+    "scheduled"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Array of tag names or IDs to associate with the post. On update, this fully replaces the existing tags array (not merged).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / title

Added value: +{
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / twitter_description

Added value: +{
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / twitter_image

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / twitter_title

Added value: +{
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / visibility

Added value: +{
+  "default": "public",
+  "enum": [
+    "public",
+    "members",
+    "paid",
+    "tiers"
+  ],
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "id"
+]
```

First observedv1.0.0Jan 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description must convey behavioral traits. It discloses partial update behavior and replacement semantics for tags and authors. Missing details on authorization, rate limits, or side effects, but adequate for a straightforward update.

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 concise sentences, front-loaded with the action and scope. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 28 parameters, no annotations, and no output schema, the description is somewhat minimal. It covers the update behavior and replacement caveat but omits details on required id, return value, and error handling. Adequate but not comprehensive.

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 only 21%, so many parameters lack descriptions. The description adds value by mentioning updateable categories but does not detail individual parameters beyond tags/authors. It does not fully compensate for the low coverage.

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 it updates an existing post in Ghost CMS and lists the types of fields (title, content, status, tags, images, SEO). This distinguishes it from create, delete, and page update siblings.

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?

The description explicitly notes that omitted fields remain unchanged and tags/authors are fully replaced, which guides usage. It does not explicitly state when to use vs alternatives like ghost_update_page, but the name and context make it clear.

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

ghost_update_post

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools