BlogSEO

Get article

get_article

Read-onlyIdempotent

Returns one article: headline, slug, status, target keyword, meta description, cover image and its alt text (main_image_alt, shared by every locale), dashboard URL and the list of its translations. Set include_content=true to also get the markdown body (can be long). Pass locale to read a translation instead of the default-language version; the base status and slug are shared by every locale. Never contacts the CMS. 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.
`include_content`	No	Also return the article body as markdown.

Output Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes
`locale`	Yes	Locale of the returned version; null for the default language.
`status`	Yes	Raw status; status_label is the human reading.
`excerpt`	Yes
`headline`	Yes
`is_on_cms`	Yes	true once the article exists on a connected CMS.
`article_id`	Yes
`created_at`	Yes
`website_id`	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.
`translations`	Yes
`dashboard_url`	Yes	Article page in the app.
`default_locale`	Yes
`is_out_of_sync`	Yes	Edited since the last push to the CMS; sync_article_to_cms clears it.
`main_image_alt`	Yes	Cover alt text, shared by every locale.
`main_image_url`	Yes	Cover image URL.
`target_keyword`	Yes
`last_updated_at`	Yes
`includes_content`	Yes	true when markdown_content holds the body.
`markdown_content`	Yes	The article body in markdown when include_content=true, null otherwise.
`meta_description`	Yes
`target_keyword_id`	Yes
`main_image_description`	Yes	Brief the cover image was generated from.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

changedOutput schema / properties / includes_content / description

Previous value: -"true when the markdown body is in the text content."New value: +"true when markdown_content holds the body."

addedOutput schema / properties / markdown_content

Added value: +{
+  "description": "The article body in markdown when include_content=true, null otherwise.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

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",
-  "website_id",
-  "dashboard_url",
-  "last_updated_at",
-  "is_on_cms",
-  "excerpt",
-  "main_image_description",
-  "main_image_alt",
-  "target_keyword_id",
-  "default_locale",
-  "locale",
-  "translations",
-  "includes_content"
-]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",
+  "website_id",
+  "dashboard_url",
+  "last_updated_at",
+  "is_on_cms",
+  "excerpt",
+  "main_image_description",
+  "main_image_alt",
+  "target_keyword_id",
+  "default_locale",
+  "locale",
+  "translations",
+  "includes_content",
+  "markdown_content"
+]

First observedSep 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lowered, yet the description adds real value: "Never contacts the CMS" clarifies the data source, and the warning that the content body "can be long" prepares the agent for payload size. It also notes the sharing semantics of status/slug across locales.

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-loaded with the return contents, then the optional-parameter guidance, with no filler sentences. The field enumeration and locale/cross-locale notes make it somewhat dense, but every clause carries information.

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 explained, yet the description covers the locale fallback, the multi-website disambiguation via website_id, and the content-size caveat. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: main_image_alt and the base status/slug are shared by every locale, and include_content can yield a long body. That sharing behavior is not captured in the parameter descriptions themselves.

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 ("Returns one article") and enumerates the returned fields, which lets an agent distinguish it from list_articles without opening the schema. The scope is single-article retrieval, clearly separated from the sibling list/batch tools.

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 explicit conditions for the optional parameters: include_content for the markdown body, locale to read a translation, website_id when the account has several websites, plus a pointer to get_account. It does not name a competing alternative tool directly, but the context needed to invoke it correctly is present.

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.