Skip to main content
Glama
dataforseo

DataForSEO MCP Server

Official
by dataforseo

Backlinks Backlinks

backlinks_backlinks
Read-onlyIdempotent

Retrieve a list of backlinks and associated data for any domain, subdomain, or webpage. Filter by rank, dofollow status, and more to analyze link profiles.

Instructions

This endpoint will provide you with a list of backlinks and relevant data for the specified domain, subdomain, or webpage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoresults grouping type optional field possible grouping types: as_is – returns all backlinks one_per_domain – returns one backlink per domain one_per_anchor – returns one backlink per anchor default value: as_isas_is
limitNothe maximum number of returned backlinks
offsetNooffset in the results array of the returned backlinks optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks
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://)
filtersNoArray-based filter expression. A single condition is a 3-element array: [field, operator, value]. Combine conditions with ["and"|"or"] between them: [condition, "and", condition]. Max 8 filters. Operators: =, <>, in, not_in, like, not_like, ilike, not_ilike, regex, not_regex, match, not_match Use % with like/not_like to match any string of zero or more characters. Examples: Single: ["rank",">","80"] Combined: [["page_from_rank",">","55"],"and",["dofollow","=",true]]
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"]
Behavior3/5

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

Annotations already declare it as read-only, idempotent, and non-destructive. The description adds only 'list of backlinks and relevant data,' which is minimal. No contradiction with annotations, but no extra behavioral context beyond what annotations provide.

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?

Single sentence, direct, front-loaded with key information. No unnecessary words.

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?

Description is too brief for a tool with 6 parameters and no output schema. It does not indicate what 'relevant data' includes, such as anchor text, domain rating, or other fields. Users need more context to understand the return structure.

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 baseline is 3. The description does not add any meaning beyond what the schema already explains about parameters like mode, limit, offset, etc.

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?

Clearly states it provides a list of backlinks for a specified domain, subdomain, or webpage. The verb 'provide' and resource 'backlinks' are specific, and it distinguishes from sibling tools like backlinks_anchors or backlinks_summary.

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 on when to use this tool versus alternatives. With many sibling tools like backlinks_domain_intersection or backlinks_referring_domains, the description should indicate when to choose this one.

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/dataforseo/mcp-server-typescript-deprecated'

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