SE Ranking MCP Server

Get Page Authority

DATA_getPageAuthority

Retrieve the InLink Rank (Page Authority) for a target URL. Assess link popularity to evaluate page authority for SEO analysis.

Instructions

Data Tool: Returns information about the InLink Rank (Page Authority) for a target URL.

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": {
      "target": "<target>"
    },
    "name": "DATA_getPageAuthority"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes	Aim of the request: root domain, host, or URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 7, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations present, the description bears full responsibility for disclosing behavioral traits. It only states 'Returns information' without specifying whether the operation is read-only, if authentication is needed, rate limits, or any side effects. This is insufficient for a data retrieval tool.

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 brief at two sentences, with the first sentence ('Data Tool:') being redundant. The core information is front-loaded, but the filler slightly detracts from conciseness. Overall, it is efficient.

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

Completeness3/5

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

Given the tool's simplicity (single parameter) and lack of output schema, the description should clarify what the return value includes. It mentions 'InLink Rank (Page Authority)' but does not specify other possible fields or format. This is adequate but not thorough.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter description; in fact, it says 'target URL' but the schema allows root domain or host, causing slight ambiguity. No value added beyond schema.

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 returns information about InLink Rank (Page Authority) for a target URL, using a specific verb and resource. It distinguishes from sibling tools like DATA_getDomainAuthority (domain-level) and DATA_getPageAuthorityHistory (history), making the purpose unambiguous.

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 is provided on when to use this tool versus alternatives such as DATA_getDomainAuthority or DATA_getPageAuthorityHistory. The description lacks context on prerequisites, when not to use it, or which scenarios it suits best.

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

Deploy Server