Ghost MCP Server

ghost_create_tag

Create a new tag for your Ghost CMS blog with customizable visibility, meta data, and design options.

Instructions

Creates a new tag in Ghost CMS.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	Yes
`slug`	No
`description`	No
`feature_image`	No
`visibility`	No	public
`meta_title`	No
`meta_description`	No
`og_image`	No
`og_title`	No
`og_description`	No
`twitter_image`	No
`twitter_title`	No
`twitter_description`	No
`codeinjection_head`	No
`codeinjection_foot`	No
`canonical_url`	No
`accent_color`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed19 schema fields changedv1.12.2Apr 29, 2026

addedInput schema / $schema

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

addedInput schema / properties / accent_color

Added value: +{
+  "pattern": "^#[0-9A-Fa-f]{6}$",
+  "type": "string"
+}

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 / description

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

addedInput schema / properties / feature_image

Added value: +{
+  "format": "uri",
+  "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 / name

Added value: +{
+  "maxLength": 191,
+  "minLength": 1,
+  "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 / slug

Added value: +{
+  "pattern": "^[a-z0-9-]+$",
+  "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: +[
+  "name"
+]
```

First observedv1.0.0Jan 4, 2026

TDQS

C2.1/5.0

Behavior1/5

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

No annotations are provided, and the description gives no behavioral details such as required permissions, side effects, or constraints. The description fails to compensate for the lack of annotations.

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

Conciseness2/5

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

The description is extremely short but at the cost of being under-specified. It is not appropriately sized for the tool's complexity; it should provide more context without being verbose.

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?

Given the tool has 17 parameters and no output schema, the description is severely incomplete. It does not address key aspects like required fields, behavior, or return values.

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 0% description coverage, and the description adds no information about any parameters. It does not help the agent understand the meaning or usage of the 17 parameters.

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 clearly states the verb 'creates' and the resource 'tag' in the context of Ghost CMS. However, it does not differentiate from sibling tools like ghost_create_post, but the name already implies the resource.

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 provided on when to use this tool versus alternatives. There are no exclusions or usage context mentioned.

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

ghost_create_tag

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools