BlogSEO

Update article slug

update_article_slug

Idempotent

Changes the URL slug of an article; the value is normalised (lowercase, hyphens) and must be unique on the website. Translations share the parent slug, so there is no locale option. 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. On a published article the old slug is kept as a redirect on the hosted blog only; other CMSs will serve a 404 on the old URL. Pass website_id when the account has several websites (see get_account).

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	New slug, e.g. "best-running-shoes".
`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.6/5.0

Behavior5/5

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

Annotations only declare it is a non-read-only, idempotent, non-destructive write. The description goes well beyond that, disclosing slug normalisation (lowercase/hyphens), website-wide uniqueness, shared parent slug for translations, the Out of Sync side effect on published articles, and differing redirect behavior (hosted blog keeps redirect, other CMSs 404). This is exactly the behavioral depth that earns a high score.

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?

A single dense paragraph with the core action front-loaded and no filler sentences; every clause adds operational value. It could be marginally easier to scan if broken up, which keeps it just under a top mark.

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 full set of things an agent must know before calling: normalisation, uniqueness constraint, translation/locale behaviour, side effects on published articles, and how to recover via sync_article_to_cms or republish.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains slug normalisation and uniqueness beyond the schema's bare example, clarifies there is no locale option (relevant to the slug parameter), and gives the conditional rule for website_id.

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 ('Changes the URL slug of an article') and immediately distinguishes itself from sibling mutators like update_article_content and update_article_headline by naming the exact field it touches. An agent can identify the tool without opening the schema.

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?

Provides clear scenario-based context: pass website_id when the account has several websites (pointing to get_account), and use sync_article_to_cms when a published article goes Out of Sync. It doesn't explicitly rule out alternative tools, but the when/why guidance is concrete and actionable.

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.