Skip to main content
Glama

ghost_upload_image

Upload an image to Ghost CMS from a URL, local file, or base64 data. Returns the image URL, alt text, and reference.

Instructions

Uploads an image to Ghost CMS. Accepts a remote URL, a local file path (when GHOST_MCP_IMAGE_ROOT is configured), or a base64 payload. Returns the Ghost image URL, alt text, and ref (when Ghost echoes it).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageUrlNoThe publicly accessible URL of the image to download and upload.
imagePathNoAbsolute path to a local image file. Only accepted when the GHOST_MCP_IMAGE_ROOT env var is set; paths must resolve inside that root.
imageBase64NoBase64-encoded image bytes (with or without data: URI prefix). Decoded size capped at 5MB to respect MCP transport limits. Requires mimeType.
mimeTypeNoMIME type for imageBase64 input (e.g. image/png, image/jpeg, image/svg+xml). Required when imageBase64 is used.
altNoAlt text for the image. If omitted, a default will be generated from the filename.
purposeNoIntended use. Ghost validates format/size per purpose (icon/profile_image must be square; icon also accepts ICO).
refNoCaller-supplied identifier (e.g. original filename). Ghost echoes it back in the response.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses env var requirement for local paths, base64 size cap (5MB), mimeType requirement, and return fields. Could add more on error handling or auth, but sufficient.

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

Conciseness5/5

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

Three concise sentences: purpose, input methods with conditions, return values. No unnecessary words, front-loaded with key info.

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

Completeness4/5

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

No output schema, but description mentions return fields (URL, alt, ref). Complexity is moderate with 7 params; description covers input constraints and output format adequately.

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

Parameters4/5

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

Schema covers 100% of parameters with descriptions. The description adds value by explaining conditional constraints (env var for imagePath, size cap and mimeType for imageBase64, Ghost validation for purpose).

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 'Uploads an image to Ghost CMS' and specifies three input methods (URL, local path, base64). It distinguishes from siblings which are CRUD on other entities, not image upload.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists input methods with conditions (e.g., local file requires GHOST_MCP_IMAGE_ROOT, base64 requires mimeType). It doesn't explicitly contrast with alternatives, but no sibling tool does image upload, so guidance is adequate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jgardner04/Ghost-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server