Skip to main content
Glama

ghost_set_feature_image

Uploads an image and sets it as the feature image of a post or page in one call, with optional alt text and caption. Accepts image URL, local path, or base64 input.

Instructions

Uploads an image and assigns it as the feature image of a post or page (with optional alt text and caption) in one call. Accepts the same imageUrl/imagePath/imageBase64 input modes as ghost_upload_image. Returns the updated resource. If the update fails after the upload, the error response includes the orphaned image URL.

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.
typeYesWhich resource to attach the feature image to.
idYesID of the post or page.
captionNoOptional HTML caption for the feature image (max 5000 chars).
Behavior4/5

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

No annotations, but description discloses upload-then-assign order and orphaned image URL on failure. Adequate for a mutation tool, though auth and rate limits not mentioned.

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?

Two sentences, no fluff. First sentence states core action, second provides error handling detail. Efficient and front-loaded.

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 notes returns updated resource. For 10-param tool with no annotations, description covers key behavioral and error info 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 coverage 100%, description adds context (e.g., same input modes as ghost_upload_image, alt default from filename). Adds value beyond schema.

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 states verb (uploads and assigns), resource (feature image of post/page), and distinguishes from ghost_upload_image by combining both actions in one call.

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?

Clearly describes the one-call convenience and mentions same input modes as ghost_upload_image, implicitly guiding when to use it. Could explicitly state alternatives but sufficient.

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