Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_anchors

Analyze anchor text distribution for any website's backlinks to understand link building strategies and optimize SEO performance.

Instructions

This endpoint will provide you with a detailed overview of anchors used when linking to the specified website with relevant backlink data for each of them

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNoarray of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: =, <>, in, not_in, like, not_like, ilike, not_ilike, regex, not_regex, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: ["rank",">","80"] [["page_from_rank",">","55"], "and", ["dofollow","=",true]] [["first_seen",">","2017-10-23 11:31:45 +00:00"], "and", [["anchor","like","%seo%"],"or",["text_pre","like","%seo%"]]]
limitNothe maximum number of returned anchors
offsetNooffset in the results array of returned anchors optional field default value: 0 if you specify the 10 value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors
order_byNoresults sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ["rank,desc"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["domain_from_rank,desc","page_from_rank,asc"]
targetYesdomain, subdomain or webpage to get backlinks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While it mentions the tool 'will provide' data (implying a read operation), it doesn't address important behavioral aspects: whether this is a live query or cached data, rate limits, authentication requirements, pagination behavior (beyond what's in the schema), error conditions, or what 'detailed overview' specifically includes. For a data retrieval tool with complex filtering capabilities, this leaves significant gaps.

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 a single, reasonably concise sentence that gets straight to the point. It front-loads the core purpose without unnecessary preamble. However, it could be slightly more structured by separating the 'what' from the 'why' - for example, explicitly stating this is for analyzing anchor text distribution in backlink profiles.

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?

Given the complexity (5 parameters with rich filtering capabilities), absence of annotations, and lack of output schema, the description is insufficiently complete. It doesn't explain what data fields are returned in the 'detailed overview', how the anchor data is structured, whether results include metrics like anchor frequency or distribution, or provide any examples of typical use cases. For a specialized SEO tool with many sibling alternatives, users need more context to understand what they're getting.

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 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema - it doesn't explain how 'target' relates to 'anchors', what 'detailed overview' means in terms of output fields, or provide examples of typical filter combinations for anchor analysis. The baseline of 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'provide you with a detailed overview of anchors used when linking to the specified website with relevant backlink data for each of them'. It specifies the verb ('provide'), resource ('anchors'), and scope ('linking to the specified website'), making it clear this tool retrieves anchor text data for backlinks. However, it doesn't explicitly differentiate from sibling tools like 'backlinks_backlinks' or 'backlinks_summary', which likely provide different backlink data aspects.

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?

The description offers no guidance on when to use this tool versus alternatives. With 24 sibling tools in the backlinks category, there's no mention of what distinguishes this anchor-focused tool from others like 'backlinks_backlinks' (likely general backlink data) or 'backlinks_summary' (likely aggregated metrics). The description assumes the user knows when anchor-specific data is needed without providing context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cortex8/oyt-dataforseo-mcp-worker'

If you have feedback or need assistance with the MCP directory API, please join our Discord server