Rankwise

Replace an article

replace_article

DestructiveIdempotent

Replace an article's title, meta description, slug or full HTML body. Send only the fields to change. The slug must be unique in the workspace, and a published article keeps its slug. Open tracked changes are dropped when the body changes. This saves the article in Rankwise; live_update and next_step in the result say how a published article's live post takes the edit. update_live_post updates the live post in place on WordPress (Rankwise plugin), Next.js (@rankwise/next), Rails (rankwise-rails), the webhook integration and Shopify. On the Rankwise-hosted blog and Framer a saved edit is already live (Framer at its next sync), so there is nothing to push. Webflow, Wix, Notion, Ghost and WordPress.com cannot update a live post from Rankwise: change the post in that CMS by hand. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "article_id": "<article_id>"
    },
    "name": "replace_article"
  }
}

Input Schema

Name	Required	Description
`html`	No	The full article body as HTML. It is sanitised: scripts, styles, frames, forms and event handlers are removed.
`slug`	No
`title`	No
`article_id`	Yes
`meta_description`	No

Output Schema

Name	Required	Description	Default
`article`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- addedOutput schema / properties / article / properties / live_update
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / article / properties / next_step
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the destructive and idempotent annotations, the description discloses important side effects: open tracked changes are dropped when the body changes, slugs must be unique, and published articles keep their slug. It also explains save-versus-live propagation behavior across platforms.

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?

The description is front-loaded with purpose, fields, and key constraints before moving to live-update behavior. The platform roster is decision-relevant but somewhat sprawling, and the trailing 'Free.' is abrupt rather than fully integrated.

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 destructive, cross-platform save operation, the description covers the essential distinction between saving in Rankwise and propagating to live posts, plus platform limitations. With annotations and an output schema documenting live_update and next_step, it is complete enough for an agent to call correctly.

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 only 20%, and the description adds useful meaning for slug uniqueness, published-slug immutability, and the partial-update rule 'Send only the fields to change'. However, it does not explain article_id or title/meta_description semantics, so meaningful parameter gaps remain.

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?

The description states a specific verb and resource: replacing an article's title, meta description, slug, or HTML body. It is clearly differentiated from sibling update_live_post by explaining that this tool saves in Rankwise while update_live_post pushes live-post changes to supported CMSs.

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?

It explicitly explains the workflow: save the edit in Rankwise, then use live_update/next_step or update_live_post depending on the platform. It also names platform alternatives and says when a live post must be changed by hand instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rankwise 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.