Skip to main content
Glama
Sign In
outrank-mcp

outrank-mcp

by NoBanks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_article_content

Retrieve the raw markdown and HTML content of a completed article using its unique ID. Access the generated article in both formats for further use.

Instructions

Fetch the raw markdown and HTML content for a finished article by its ID.

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": "get_article_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYesThe unique article ID from generate_article

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Without annotations, the description carries full burden. It discloses that the article must be 'finished' (a behavioral constraint) and returns both markdown and HTML. However, it doesn't specify error handling, prerequisites, or what happens for unfinished articles, leaving gaps.

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 a single, front-loaded sentence with no waste. Every word is necessary to convey the tool's function.

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

Completeness4/5

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

For a simple fetch tool with one parameter and no output schema, the description covers the main purpose and a key constraint (article must be finished). Minor omissions like error behavior prevent a perfect score, but it's largely complete.

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 100% for the single parameter. The description adds the context 'from generate_article', which links to a sibling, but this is minor. The schema already describes the parameter as 'The unique article ID', so the description adds limited extra meaning.

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 clearly states the tool fetches 'raw markdown and HTML content' for a 'finished article' by ID, distinguishing it from siblings like generate_article which creates articles, and list_products which lists products. The verb 'Fetch' and resource 'content' are specific.

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

Usage Guidelines3/5

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

The description implies usage after article generation (IDs from generate_article), but lacks explicit when-to-use or when-not-to-use guidance. No alternatives or exclusions are mentioned, making it merely adequate.

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