BlogSEO

Set article cover image

set_article_cover_image

Replaces the cover (main) image of a generated article with an image stored on the website's media host: either downloaded from a public URL (image_url) or uploaded from the user's machine (upload_id, see create_image_upload). Pass alt_text to describe the new image at the same time (recommended). Pass locale to change the cover of a translation only. Free. Editing an article that is already published (or published in draft) marks it Out of Sync until it is synced with sync_article_to_cms or published again. Inline images inside the body are part of the markdown: host them with upload_article_image and edit the body with update_article_content. Pass website_id when the account has several websites (see get_account).

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Translation locale (e.g. "fr") to target instead of the default-language article.
`alt_text`	No	Alt text of the cover image (max 200 characters): what the image shows, for search engines and screen readers. Shared by every locale of the article and sent to the CMS with the image.
`image_url`	No	Public http(s) URL of the image to download (JPEG, PNG, WebP, GIF or AVIF, 4 MB max). For a file on the user's machine, pass upload_id instead.
`upload_id`	No	upload_id returned by create_image_upload, once the file has been sent to its upload_url. Alternative to image_url for files on the user's machine (10 MB max).
`article_id`	Yes	Article id from list_articles.
`website_id`	No	Website id from get_account. Optional when the account has a single website.

Output Schema

TableJSON Schema

Name	Required	Description
`locale`	Yes
`article`	Yes
`main_image_url`	Yes	Hosted URL of the new cover.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already signal readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description adds meaningful behavioral context: it marks the article Out of Sync when published, mentions Free, and clarifies that alt_text is shared across locales. The description is consistent with the annotations (a mutation that is not idempotent) and goes beyond them.

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?

The description is compact given the tool's complexity and delivers the key differentiators up front. The sentence about inline images is ancillary but prevents a common misuse, and the flow references are terse. It could be slightly tighter, but the density is high and valuable.

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?

The tool has six parameters, no enums, a rich schema, and a true output schema. The description covers the two source modes, the out-of-sync side effect, the publishing distinction, translation targeting, multi-website handling, and routes inline-image work to sibling tools. There is no meaningful gap for an agent to call this correctly.

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 is 100%, so the schema already explains parameters well. The description still adds useful semantics: it clarifies the relationship between image_url and upload_id as mutually exclusive alternatives, recommends alt_text, describes locale as targeting a translation, and notes website_id is only needed for multi-website accounts. This exceeds the schema's per-parameter descriptions.

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 opens with a precise verb ('Replaces') and resource ('the cover (main) image of a generated article'), and distinguishes itself from sibling tools like upload_article_image and update_article_cover_alt_text. It makes the core purpose immediately identifiable.

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

Usage Guidelines5/5

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

The description provides clear when-to-use guidance: it explains the two image source options (URL vs upload_id), refers to create_image_upload for the upload flow, mentions website_id for multi-website accounts, and tells agents to use upload_article_image plus update_article_content for inline images instead. This is explicit routing with conditions and alternatives.

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

All BlogSEO tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.