Skip to main content
Glama
jgardner04

Ghost MCP Server

by jgardner04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ghost_update_member

Updates an existing member's details in Ghost CMS, including email, name, subscription status, and labels. All fields are optional except the member ID.

Instructions

Updates an existing member in Ghost CMS. All fields except id are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
emailNo
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. Changed10 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 / id
      Added value: +{
+  "pattern": "^[a-f0-9]{24}$",
+  "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: +[
+  "id"
+]
  4. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations provided. Description only states 'updates' but does not disclose error handling (e.g., missing member), partial update behavior, or side effects. Minimal behavioral context.

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?

Description is brief and front-loaded but lacks elaboration on update behavior. Not overly verbose, but could be slightly more structured.

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?

With 8 parameters and no output schema, description is insufficient. Does not explain return values, error cases, or behavior when optional fields are omitted. Inadequate for a complex update tool.

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 50% (4 of 8 params have descriptions). Description adds no additional meaning beyond schema, only restating that optional fields exist. Baseline score due to partial 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?

Description clearly states verb 'updates' and resource 'existing member in Ghost CMS'. It distinguishes from sibling tools like ghost_create_member and ghost_get_member by specifying 'existing' and 'update'.

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 explicit guidance on when to use this tool vs alternatives. Does not mention prerequisites or conditions for updating (e.g., member must exist). Lacks when-not-to-use 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