BlogSEO

Edit article with AI

edit_article_with_ai

Destructive

Rewrites an article's body with AI following your instructions (tone, length, add a section, fix facts...) and saves it. Targets the default-language version unless locale is given; also_apply_to_locales runs the same instructions on extra translations, one credit each. Synchronous and slow: the call takes one to several minutes, wait for it instead of retrying. 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. Only locales that were actually rewritten are charged. Use batch_edit_articles_with_ai for many articles, and the update_* tools for headline, meta description or slug. Costs AI brain credits (see the cost rule above), charged after the work, not refunded on failure. Requires an active subscription or free trial. Pass confirm=true to acknowledge the AI brain credits charge; without it the tool only returns the cost and your balance. 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.
`confirm`	No	Set to true to acknowledge the AI brain credit charge. Omit it to only get the cost and your balance.
`article_id`	Yes	Article id from list_articles.
`website_id`	No	Website id from get_account. Optional when the account has a single website.
`instructions`	Yes	What to change in the article.
`also_apply_to_locales`	No	Extra translation locales to rewrite with the same instructions (one credit each).

Output Schema

TableJSON Schema

Name	Required	Description
`article_id`	No
`edited_locales`	No	Locales that were rewritten and charged.
`failed_locales`	No
`credits_balance`	No	Current AI brain credits balance; only with requires_confirmation.
`credits_charged`	No
`credits_required`	No	AI brain credits the call would charge; only with requires_confirmation.
`credits_balance_after`	No	AI brain credits balance after this call.
`requires_confirmation`	No	Present when the tool did not run: it needs confirm=true. The other fields are then absent.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A5/5.0

Behavior5/5

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

Goes far beyond annotations by disclosing synchronous slow execution ('one to several minutes, wait for it instead of retrying'), the Out of Sync side effect and remedy, credit charging and refund policy, subscription requirement, and the cost-estimate behavior when confirm is omitted. The destructiveHint is consistent with these details; no contradiction.

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?

The description is dense but every sentence earns its place. It front-loads the core action and then methodically covers timing, side effects, costs, prerequisites, and parameter conditions without fluff.

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?

For a slow, destructive, credit-charging AI editing tool with 6 parameters, the description covers all critical operational aspects: duration, charging behavior, side effects, prerequisites, and parameter usage. An agent has everything needed to invoke it safely and correctly; the output schema handles return-value specifics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Even though schema coverage is 100%, the description adds essential semantics: locale target selection, per-locale credits for also_apply_to_locales, confirm's dual role (acknowledge vs. cost-only response), and website_id's condition. It also clarifies instructions with concrete examples ('tone, length, add a section, fix facts...').

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: 'Rewrites an article's body with AI... and saves it.' The description also names sibling alternatives (batch_edit_articles_with_ai, update_* tools), so an agent can immediately distinguish this tool from related ones.

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 gives when-to-use and when-not-to-use guidance: 'Use batch_edit_articles_with_ai for many articles, and the update_* tools for headline, meta description or slug.' Also explains when to pass confirm, website_id, and locale, making invocation decisions clear.

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.