BlogSEO

Update article headline

update_article_headline

Idempotent

Renames an article (or one of its translations when locale is given). 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. Renaming an article that already lives on a CMS freezes its current slug so the live URL does not move; use update_article_slug to change the URL on purpose. 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.
`headline`	Yes	New headline.
`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.7/5.0

Behavior5/5

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

Discloses non-obvious side effects well beyond the annotations: editing a published (or draft-published) article marks it Out of Sync, and renaming a CMS-live article freezes the slug so the live URL does not move. These facts about state and irreversible URL anchoring are exactly what an agent needs and cannot infer from the schema.

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, each carrying distinct information, with the core rename behavior front-loaded and the side-effect and sibling-routing details following. No filler.

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 not be described. Combined with full schema coverage and annotations, the description supplies everything an agent needs: scope, side effects, alternatives, and the multi-website condition.

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 description coverage is 100%, so the parameters are already fully documented. The description adds useful framing for locale (target a translation) and website_id (multi-website accounts), but does not go beyond what the schema states, warranting the baseline 3.

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 ("Renames an article") and extends it precisely to translations via the locale parameter. It is immediately distinguishable from siblings like update_article_slug and update_article_content.

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?

Explicitly routes the agent: use update_article_slug to intentionally change the URL, and sync_article_to_cms or republish when the article goes Out of Sync. It also names the condition (multiple websites) that governs passing website_id, with get_account as the lookup.

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.