Rankwise

Generate article

generate_article

Destructive

Write a new AI article for a keyword. It uses the same research-and-cite writer as Autopilot: real sources, links only to pages that exist, a closing call to action, and Article and FAQ schema. This spends workspace credits (1 for short, 2 for medium, 3 for long, 4 for comprehensive; check get_plan_and_credits first). The article is generated in the background and is NOT published: call publish_article for that. Retries with the same idempotency_key never spend twice.

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": {
      "keyword": "<keyword>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "generate_article"
  }
}

Input Schema

Name	Required	Description
`tone`	No
`length`	No	short 1,200-1,600 words, medium 1,600-2,400 (default), long 2,400-3,200, comprehensive 3,200-4,200
`keyword`	Yes	The topic or search keyword
`language`	No
`article_type`	No	auto (default, chosen from the keyword), how_to, explainer, comparison, reference or listicle
`integration_id`	No	A connected CMS in this workspace, used for internal links and later publishing
`idempotency_key`	Yes

Output Schema

Name	Required	Description	Default
`article`	Yes
`next_step`	No
`credits_spent`	No
`already_existed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing credit cost per length tier, asynchronous background generation, that output is unpublished, citation behavior, and schema generation. The one nit is the idempotency_key dedup claim sitting against idempotentHint=false, though this is explicable as keyed dedup rather than a true contradiction. No mention of auth/permission requirements or failure behavior.

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?

Every sentence earns its place: purpose, fidelity, cost, async/unpublished status, and idempotency. Front-loaded with the core action and no filler.

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 described, and the annotations carry the safety profile. Between them and the description's cost, async, and publish-status notes, an agent has everything needed to call it correctly.

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?

Adds real meaning beyond the schema: the per-length credit mapping (1/2/3/4 credits) and the idempotency_key retry semantics are not in the schema. However, tone, language, article_type and integration_id are left entirely to the schema, so coverage of the parameter set is partial at 57%.

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?

Opening sentence is a specific verb+resource ("Write a new AI article for a keyword") and the body makes clear it produces a draft, distinguishing it from publish_article and replace_article. An agent can identify the tool's job 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names prerequisites and alternatives explicitly: check get_plan_and_credits first for credit balance, and call publish_article to publish since generation does not publish. The routing condition against the sibling is stated, not inferred.

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.