Skip to main content
Glama
Sign In

Seo Backlinks

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Seo Backlinks Anchors

seo_backlinks_anchors
Read-onlyIdempotent

Anchor-text distribution for <domain> — the anchor texts used in backlinks to a target, each with backlink and referring-domain counts, via DataForSEO. "What anchor text do links to this site use". Example: seo_backlinks_anchors({ target: "nike.com", limit: 50, _apiKey: "your-base64-key" })

Input Schema

NameRequiredDescriptionDefault
limitNoMax anchors to return (default 50, max 200)
targetYesDomain, subdomain, or URL, e.g. "nike.com"
_apiKeyYesDataForSEO API key = base64("login:password")
backlinks_status_typeNo"live" (default), "all", or "lost"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-seo-backlinks-api-key",
+    "limit": 50,
+    "target": "nike.com"
+  },
+  {
+    "_apiKey": "your-seo-backlinks-api-key",
+    "backlinks_status_type": "live",
+    "limit": 75,
+    "target": "example.com"
+  }
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds that it uses the DataForSEO API and provides the output structure (anchor texts with counts), which adds context beyond the annotations.

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 concise with one explanatory sentence, a natural language query, and an example. The query phrase is slightly redundant but not harmful. Overall well-structured and front-loaded.

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?

No output schema is provided; the description hints at output fields but does not specify structure or pagination. For a tool with 4 parameters and moderate complexity, the description is adequate but leaves gaps in output expectations.

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 description coverage is 100%, so the schema already documents all parameters. The description adds an example but no new semantic information beyond what the schema provides. Baseline 3 is appropriate.

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 it returns anchor-text distribution with backlink and referring-domain counts, using a specific verb phrase. It distinguishes from siblings like seo_backlinks_list (lists backlinks) and seo_backlinks_summary (summary stats) by focusing on anchor texts.

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 explicit guidance on when to use this tool versus other SEO backlink tools. The description does not mention alternatives or scenarios where this tool is preferred.

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

All Seo Backlinks toolsInspect
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.

Resources