Skip to main content
Glama
zecloud
by zecloud

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GHOST_API_URLYesBase URL of your Ghost site, e.g. https://yourblog.ghost.io
GHOST_API_VERSIONNoAPI version, defaults to v5.0v5.0
GHOST_ADMIN_API_KEYYesAdmin API key (Ghost Admin → Settings → Integrations → Add custom integration)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
posts_browseD–
posts_readD–
posts_addD–
posts_editD–
posts_deleteD–
members_browseD–
members_readD–
members_addD–
members_editD–
members_deleteD–
users_browseD–
users_readD–
users_editD–
users_deleteD–
tags_browseD–
tags_readD–
tags_addD–
tags_editD–
tags_deleteD–
tiers_browseD–
tiers_readD–
tiers_addD–
tiers_editD–
tiers_deleteD–
offers_browseD–
offers_readD–
offers_addD–
offers_editD–
offers_deleteD–
newsletters_browseD–
newsletters_readD–
newsletters_addD–
newsletters_editD–
newsletters_deleteD–
invites_browseD–
invites_addD–
invites_deleteD–
roles_browseD–
roles_readD–
webhooks_addD–
webhooks_editD–
webhooks_deleteD–

Prompts

Interactive templates invoked by user choice

NameDescription
summarize-post

Resources

Contextual data attached and managed by the client

NameDescription
blog-info

TDQS

D1.8/5.0

Scored across 42 tools

Disambiguation4/5

Tools follow a resource_action pattern that clearly separates resources (posts, members, tags) and CRUD-like operations (browse, read, add, edit, delete). Boundaries are mostly clear, though browse vs read distinction is slightly ambiguous without descriptions.

Naming Consistency5/5

Every tool consistently uses resource_action format with plural resources and a small fixed verb set (browse, read, add, edit, delete). No mixing of conventions.

Tool Count2/5

42 tools is heavy for a Ghost CMS surface, and many are mechanical per-resource variants. This bloats the toolset beyond what an agent can easily navigate.

Completeness3/5

Coverage is good across many resources, but many resources lack edit/delete (newsletters has no browse? invites lacks read/edit; users lacks add; webhooks lack browse/read). No descriptions make gaps harder to assess, but lifecycle coverage is uneven.

Maintenance

ActivityStale
ResponsivenessNo issues