backlinksAuthorityRetrieve authority metrics for a domain, subdomain, or full URL. Get backlink-based authority scores to evaluate link strength and inform SEO strategy.
Fetch authority metrics for a target (domain, host or URL) (v1/backlinks/authority)
| Name | Required | Description | Default |
|---|---|---|---|
| output | No | Response format. Default: json. | json |
| target | Yes | Target to assess authority: root domain, host (subdomain), or full URL. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Fetch authority metrics' which conveys a read operation, but does not disclose what metrics are included, whether the data is live or cached, or any response structure. The endpoint path in parentheses adds no behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with the core action front-loaded. It includes useful endpoint information in parentheses without any wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is insufficient for an agent to fully contextualize the tool: it lacks return value details, usage guidance relative to siblings, and clarity on what 'authority metrics' encompasses. Given the lack of output schema and annotations, this one-liner leaves too much unsaid.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both target and output parameters already described in the schema. The description adds no additional parameter semantics beyond what the schema provides, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches authority metrics for a target, with the target types explicitly listed (domain, host, or URL). This is a specific verb-resource pair, though it does not explicitly distinguish itself from siblings like domainOverview or backlinksSummary.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 the many sibling tools. The description only states what the tool does, not when it should be preferred over alternatives like domainOverview or backlinksSummary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.