Skip to main content
Glama

Create a featured image

create_featured_image

Creates a featured (hero) image in Hi, Moose for an article, sized 1200 by 630 for social sharing and the page, in the brand's saved image style when one is set. Pass the draftId returned by create_draft, or a title plus a short summary. Takes about a minute. Returns the image, a link to the PNG and alt text for the page; the file is also saved on the host device.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "create_featured_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoThe article title, when there is no draftId.
draftIdNoThe draftId returned by create_draft. Use this when the article was drafted in Hi, Moose.
projectYesThe Hi, Moose project, by its name as shown by list_projects. The projectId is also accepted.
summaryNoA short summary of the article, when there is no draftId. Up to 6000 characters.
styleIntentNoOptional: a wish for this one image (mood, scene, colours). The brand's saved image style still applies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing latency ('takes about a minute') and a real side effect the annotations don't capture: the PNG is saved on the host device. It also describes the return payload (image, PNG link, alt text). It does not explicitly warn that repeat calls create separate images, which matters given idempotentHint=false.

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 tight sentences, front-loaded with the action and format, then inputs, then cost and return value. No filler; every clause carries information.

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

Completeness5/5

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

With no output schema, the description compensates by naming what is returned (image, PNG link, alt text) and where the file lands. Prerequisites, expected duration, and required inputs are all covered for a five-parameter creative 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 coverage is 100%, so the schema already documents every parameter. The description adds the either/or relationship between draftId and title+summary and notes the brand style still applies when styleIntent is passed, but most parameter meaning lives in the 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?

States a specific verb and resource ('Creates a featured (hero) image in Hi, Moose for an article') and adds concrete scope: 1200x630, brand image style, social sharing. It is clearly distinguishable from siblings like create_draft and create_audio.

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?

Gives explicit input paths: use the draftId from create_draft, or a title plus short summary when the article wasn't drafted in Hi, Moose. It also points to list_projects for the project name. It lacks explicit when-not-to-use exclusions, but the routing is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources