Skip to main content
Glama
jgardner04

Ghost MCP Server

by jgardner04
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

ghost_create_post

Create a post in Ghost CMS with required title and HTML content, and optional configuration for slug, status, visibility, tags, authors, and more.

Instructions

Creates a new post in Ghost CMS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
htmlYesHTML content of the post
slugNo
statusNodraft
visibilityNopublic
featuredNo
feature_imageNo
feature_image_altNo
feature_image_captionNo
excerptNo
custom_excerptNo
meta_titleNo
meta_descriptionNo
og_imageNo
og_titleNo
og_descriptionNo
twitter_imageNo
twitter_titleNo
twitter_descriptionNo
canonical_urlNo
tagsNoArray of tag names or IDs to associate with the post. On update, this fully replaces the existing tags array (not merged).
authorsNoArray of author IDs or emails. On update, this fully replaces the existing authors array (not merged).
published_atNoScheduled publish time (ISO 8601 format)
codeinjection_headNo
codeinjection_footNo
custom_templateNoCustom template filename
email_onlyNoWhether post is email-only

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.14.3
  2. Removedv1.14.2
  3. Changed29 schema fields changedv1.12.2
    • 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 / 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: +[
+  "title",
+  "html"
+]
  4. First observedv1.0.0

TDQS

C2.2/5.0
Behavior1/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states the action, omitting critical details like whether the tool requires authentication, what happens on success (e.g., returns the created post object), or any side effects. The description contradicts annotations only if present (none here), so no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but given the tool's complexity (27 parameters), it is too brief to be genuinely helpful. Conciseness should not sacrifice essential information; here it does, earning a middle score.

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

Completeness1/5

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

The tool has 27 parameters, no output schema, and no annotations. The description fails to explain return values, required permissions, default behaviors (e.g., default status 'draft' is only in schema), or how to handle errors. It is grossly incomplete for the agent to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 27 parameters with only 22% description coverage (6 parameters have descriptions). The tool description adds no parameter information whatsoever. For a complex tool, this is insufficient; the description should explain key parameters or usage patterns to compensate for low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Creates a new post in Ghost CMS' clearly states the verb (creates) and resource (post), making the tool's purpose unambiguous. It distinguishes from sibling tools like ghost_create_member or ghost_create_page, each targeting different resources. However, it doesn't provide additional context beyond the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives, such as ghost_update_post for modifications or ghost_get_posts for retrieval. There is no mention of prerequisites, typical workflows, or exclusions, leaving the agent without contextual decision support.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jgardner04/Ghost-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server