Skip to main content
Glama
Sign In
outrank-mcp

outrank-mcp

by NoBanks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

generate_article

Create an SEO-optimized long-form article targeting a specific keyword, with optional auto-publish to your CMS.

Instructions

Generate a long-form SEO article targeted at a specific keyword, with optional auto-publish to the connected CMS.

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

Input Schema

NameRequiredDescriptionDefault
product_idYesThe website product ID
keywordYesTarget keyword the article will rank for
languageNoISO language codeen
auto_publishNoAuto-publish to connected CMS on completion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations; description fails to disclose side effects, errors, async behavior, or required auth/credits. Only mentions auto-publish without detail on impact.

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?

Single sentence with no waste, directly conveys core function and optional feature.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should explain return value or behavior; it does not. Lacks details on async processing, credit consumption, or error handling, leaving the agent underinformed.

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 covers all parameters (100% coverage). Description adds minimal context: 'targeted at a specific keyword' and 'auto-publish to connected CMS', but doesn't enhance individual parameter meanings.

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?

Clearly states it generates a long-form SEO article for a keyword, with optional auto-publish. Distinguishes from sibling tools like generate_keywords and get_article_content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use vs alternatives, prerequisites, or conditions. Implies keyword targeting but lacks explicit usage context.

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

Deploy Server

Other Tools