Skip to main content
Glama
jgardner04

Ghost MCP Server

by jgardner04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ghost_create_tier

Create a paid or free membership tier in Ghost CMS, setting pricing, trial days, and benefit descriptions.

Instructions

Creates a new tier (membership level) in Ghost CMS with pricing and benefits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionNo
slugNo
activeNoWhether tier is currently active/available
typeNopaid
welcome_page_urlNo
visibilityNopublic
trial_daysNoNumber of trial days for paid tiers
currencyNo
monthly_priceNo
yearly_priceNo
benefitsNoArray of benefit names/descriptions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.3
  2. Removedv1.14.2
  3. Changed14 schema fields changedv1.12.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / active
      Added value: +{
+  "default": true,
+  "description": "Whether tier is currently active/available",
+  "type": "boolean"
+}
    • addedInput schema / properties / benefits
      Added value: +{
+  "description": "Array of benefit names/descriptions",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / currency
      Added value: +{
+  "maxLength": 3,
+  "minLength": 3,
+  "pattern": "^[A-Z]{3}$",
+  "type": "string"
+}
    • addedInput schema / properties / description
      Added value: +{
+  "maxLength": 2000,
+  "type": "string"
+}
    • addedInput schema / properties / monthly_price
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "maxLength": 191,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / slug
      Added value: +{
+  "pattern": "^[a-z0-9-]+$",
+  "type": "string"
+}
    • addedInput schema / properties / trial_days
      Added value: +{
+  "default": 0,
+  "description": "Number of trial days for paid tiers",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "default": "paid",
+  "enum": [
+    "free",
+    "paid"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / visibility
      Added value: +{
+  "default": "public",
+  "enum": [
+    "public",
+    "none"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / welcome_page_url
      Added value: +{
+  "format": "uri",
+  "type": "string"
+}
    • addedInput schema / properties / yearly_price
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / required
      Added value: +[
+  "name"
+]
  4. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only states 'creates' without disclosing side effects (e.g., payment integration, irreversibility), authorization needs, or error scenarios. Important behavioral traits are omitted.

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

Conciseness4/5

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

The description is a single concise sentence, efficiently front-loading the purpose. However, it sacrifices necessary detail, which is acceptable for conciseness but impacts transparency.

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

Completeness2/5

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

Given the tool's complexity (12 parameters, no output schema, no annotations), the description is insufficient. It does not indicate return values, error conditions, or behavioral context, leaving the agent underinformed.

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

Parameters2/5

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

Schema description coverage is low (25%). The description adds no explanation of parameters beyond 'with pricing and benefits', leaving the meaning and relationships of fields like currency, prices, type, and visibility unclear.

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 the verb 'Creates' and the resource 'tier (membership level) in Ghost CMS', and specifies 'with pricing and benefits', which distinguishes it from sibling tools like ghost_create_member or ghost_create_post.

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, such as ghost_update_tier for modifications or ghost_get_tiers for retrieval. There is no mention of prerequisites or context.

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

Deploy Server

Other Tools