BlogSEO

Update article cover alt text

update_article_cover_alt_text

Idempotent

Replaces the alt text of an article's cover image. The alt text is stored once per article and used for every locale. An empty string clears it, in which case the headline is used. Inline images keep their alt text in the markdown body ( alt ): edit it with update_article_content. 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. Pass website_id when the account has several websites (see get_account).

Input Schema

TableJSON Schema

Name	Required	Description
`alt_text`	Yes	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.
`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
`slug`	Yes
`locale`	Yes	Translation locale the change applied to; null for the default-language article or a field shared by every locale. The other fields always describe the default-language article.
`status`	Yes	Raw status; status_label is the human reading.
`message`	Yes	What changed, e.g. "Headline updated for the fr version."
`headline`	Yes
`article_id`	Yes
`created_at`	Yes
`preview_text`	Yes	First 200 characters of the body.
`published_at`	Yes
`status_label`	Yes	Status as shown in the app, e.g. Published, Draft on CMS, Failed to publish.
`is_out_of_sync`	Yes	Edited since the last push to the CMS; sync_article_to_cms clears it.
`main_image_url`	Yes	Cover image URL.
`target_keyword`	Yes
`meta_description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedOutput schema / properties / locale

Added value: +{
+  "description": "Translation locale the change applied to; null for the default-language article or a field shared by every locale. The other fields always describe the default-language article.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / message

Added value: +{
+  "description": "What changed, e.g. \"Headline updated for the fr version.\"",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "article_id",
-  "headline",
-  "slug",
-  "status",
-  "status_label",
-  "created_at",
-  "published_at",
-  "is_out_of_sync",
-  "meta_description",
-  "preview_text",
-  "main_image_url",
-  "target_keyword"
-]New value: +[
+  "article_id",
+  "headline",
+  "slug",
+  "status",
+  "status_label",
+  "created_at",
+  "published_at",
+  "is_out_of_sync",
+  "meta_description",
+  "preview_text",
+  "main_image_url",
+  "target_keyword",
+  "message",
+  "locale"
+]

First observedSep 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, idempotent=true, destructive=false). The description adds non-obvious behavior the annotations cannot express: alt text is stored once and shared across all locales, an empty string clears it and falls back to the headline, and editing a published article marks it Out of Sync until synced or republished.

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?

Five sentences, each carrying distinct decision-relevant information: purpose, storage scope, empty-string edge case, sibling routing, side effect, and precondition. Purpose is front-loaded and nothing is redundant.

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?

An output schema exists so return values need no explanation. The description covers the remaining gaps an agent would hit: locale sharing, the empty-string edge case, post-publish sync state, the inline-image boundary, and multi-website disambiguation.

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 documents all three parameters, making 3 the baseline. The description still adds semantics the schema lacks: an empty alt_text is not just an empty write but an explicit clear that triggers headline fallback, and it explains when website_id is required rather than merely optional.

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?

Opens with a specific verb and resource: 'Replaces the alt text of an article's cover image.' It immediately scopes to the cover image and explicitly separates cover alt text from inline-image alt text, which is the main ambiguity in this tool family.

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?

Names the exact alternative for the adjacent case ('Inline images keep their alt text in the markdown body ... edit it with update_article_content'), states the cost ('Free'), and gives the website_id precondition plus the published-article follow-up path via sync_article_to_cms.

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.