BlogSEO

Update article meta description

update_article_meta_description

Idempotent

Replaces the SEO meta description of an article (or of one translation when locale is given); keep it under 160 characters. 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
`locale`	No	Translation locale (e.g. "fr") to target instead of the default-language article.
`article_id`	Yes	Article id from list_articles.
`website_id`	No	Website id from get_account. Optional when the account has a single website.
`meta_description`	Yes	New meta description (max 160 characters).

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: published articles are marked 'Out of Sync' until re-synced or republished, which is a non-obvious side effect an agent must plan around. It stops short of permissions or rate-limit context.

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?

Front-loads the action, then layers constraints and the side-effect warning in a compact multi-clause sentence with no filler. Dense but every clause carries information; only minor cost is a slightly run-on structure.

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?

Covers the operation, the 160-character constraint, conditional parameters, and the downstream sync consequence, and an output schema exists so return values need no explanation. Nothing an agent needs to call this correctly is missing.

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 every parameter (article_id, meta_description, locale, website_id) is already documented in the schema with sourced ids and constraints. The description largely restates the locale and website_id semantics rather than adding new meaning, so the 3 baseline applies.

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 ('Replaces the SEO meta description of an article') and immediately scopes the translation variant when locale is given. This cleanly distinguishes it from siblings like update_article_headline, update_article_slug, and update_article_cover_alt_text without requiring 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?

Gives concrete conditional guidance: pass website_id when the account has several websites, and use locale to target a single translation. It also names sync_article_to_cms as the recovery path after editing published content, but does not broadly state when to prefer this tool over manual content edits or AI-driven SEO tools.

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.