Skip to main content
Glama
jgardner04

Ghost MCP Server

by jgardner04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ghost_create_member

Create a new subscriber in Ghost CMS by providing an email address. Optionally set name, labels, newsletter subscriptions, and complimentary status.

Instructions

Creates a new member (subscriber) in Ghost CMS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes
nameNo
noteNo
subscribedNoWhether member is subscribed to newsletter
compedNoWhether member has complimentary subscription
labelsNoArray of label names to associate with member
newslettersNoArray of newsletter IDs to subscribe member to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.3
  2. Removedv1.14.2
  3. Changed9 schema fields changedv1.12.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / comped
      Added value: +{
+  "default": false,
+  "description": "Whether member has complimentary subscription",
+  "type": "boolean"
+}
    • addedInput schema / properties / email
      Added value: +{
+  "format": "email",
+  "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+  "type": "string"
+}
    • addedInput schema / properties / labels
      Added value: +{
+  "description": "Array of label names to associate with member",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "maxLength": 191,
+  "type": "string"
+}
    • addedInput schema / properties / newsletters
      Added value: +{
+  "description": "Array of newsletter IDs to subscribe member to",
+  "items": {
+    "pattern": "^[a-f0-9]{24}$",
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / note
      Added value: +{
+  "maxLength": 2000,
+  "type": "string"
+}
    • addedInput schema / properties / subscribed
      Added value: +{
+  "default": true,
+  "description": "Whether member is subscribed to newsletter",
+  "type": "boolean"
+}
    • addedInput schema / required
      Added value: +[
+  "email"
+]
  4. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the basic action without revealing side effects, duplicate handling, email sending, or permission requirements. This is insufficient for a mutation tool.

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 sentence of 8 words, front-loading the core action. It is concise but lacks necessary details; however, for the dimension of conciseness and structure, it is well-formed and easy to parse.

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 has 7 parameters, no output schema, and no annotations, the description is severely lacking. It does not explain return values, error conditions, or use context. The single sentence is insufficient for an agent to use the tool effectively.

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 description coverage is 57%, meaning the schema already describes some parameters (subscribed, comped, labels, newsletters). The description adds no additional meaning beyond the schema. According to guidelines, baseline is 3 when coverage is above 50%, and since description contributes nothing extra, score remains 3.

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 explicitly states the verb 'Creates', the resource 'new member (subscriber)', and the system 'Ghost CMS'. This clearly distinguishes it from sibling create tools like ghost_create_page 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?

The description provides no guidance on when to use this tool versus other create tools (e.g., ghost_create_newsletter) or update tools (ghost_update_member). There is no mention of prerequisites or alternative tools.

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