Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_backlinks

Retrieve backlinks data for any domain, subdomain, or webpage to analyze referring domains and anchor text for SEO insights.

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
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://)
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
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%"]]]
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"]

Implementation Reference

  • The handle() method executes the tool logic: sends a POST request to DataForSEO's /v3/backlinks/backlinks/live endpoint with the provided parameters and formats the response.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/backlinks/live', 'POST', [{
          target: params.target,
          mode: params.mode,
          limit: params.limit,
          offset: params.offset,
          filters: this.formatFilters(params.filters),
          order_by: this.formatOrderBy(params.order_by)
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • The getParams() method defines the Zod schema for input validation, including parameters like target, mode, limit, offset, filters, and order_by.
      getParams(): z.ZodRawShape {
        return {
          target: z.string().describe(`domain, 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://)`),
          mode: z.string().default("as_is").describe(`results 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_is`),
          limit: z.number().min(1).max(1000).default(10).optional().describe("the maximum number of returned backlinks"),
          offset: z.number().min(0).optional().describe(
            `offset 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`
          ),
          filters: z.array(
            z.union([
              z.array(z.union([z.string(), z.number(), z.boolean()])).length(3),
              z.enum(["and", "or"])
            ])
          ).max(8).optional().describe(
            `array 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%"]]]`      ),
          order_by: z.array(z.string()).optional().describe(
            `results 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"]`
          ),
        };
      }
  • The getTools() method instantiates BacklinksTool (line 31) and registers it using the tool's name, description, params, and handler in a record for MCP tool exposure.
    getTools(): Record<string, ToolDefinition> {
      const tools = [
        new BacklinksTool(this.dataForSEOClient),
        new BacklinksAnchorTool(this.dataForSEOClient),
        new BacklinksBulkBacklinksTool(this.dataForSEOClient),
        new BacklinksBulkNewLostReferringDomainsTool(this.dataForSEOClient),
        new BacklinksBulkNewLostBacklinksTool(this.dataForSEOClient),
        new BacklinksBulkRanksTool(this.dataForSEOClient),
        new BacklinksBulkReferringDomainsTool(this.dataForSEOClient),
        new BacklinksBulkSpamScoreTool(this.dataForSEOClient),
        new BacklinksCompetitorsTool(this.dataForSEOClient),
        new BacklinksDomainIntersectionTool(this.dataForSEOClient),
        new BacklinksDomainPagesSummaryTool(this.dataForSEOClient),
        new BacklinksDomainPagesTool(this.dataForSEOClient),
        new BacklinksPageIntersectionTool(this.dataForSEOClient),
        new BacklinksReferringDomainsTool(this.dataForSEOClient),
        new BacklinksReferringNetworksTool(this.dataForSEOClient),
        new BacklinksSummaryTool(this.dataForSEOClient),
        new BacklinksTimeseriesNewLostSummaryTool(this.dataForSEOClient),
        new BacklinksTimeseriesSummaryTool(this.dataForSEOClient),
        new BacklinksBulkPagesSummaryTool(this.dataForSEOClient),
        new BacklinksFiltersTool(this.dataForSEOClient)
        // Add more tools here
      ];
    
      return tools.reduce((acc, tool) => ({
        ...acc,
        [tool.getName()]: {
          description: tool.getDescription(),
          params: tool.getParams(),
          handler: (params: any) => tool.handle(params),
        },
      }), {});
    }
  • Imports the BacklinksTool class for use in the module.
    import { BacklinksTool } from './tools/backlinks-backlinks.tool.js';
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool 'will provide you with a list of backlinks and relevant data,' which implies a read-only operation, but it does not cover important aspects like rate limits, authentication requirements, pagination behavior (beyond parameters), error conditions, or data freshness. For a tool with 6 parameters and no annotations, this is insufficient.

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?

The description is a single, clear sentence that efficiently states the tool's purpose without unnecessary words. It is front-loaded with the core functionality and avoids redundancy. Every part of the sentence contributes directly to understanding what the tool does.

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 (6 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits (e.g., rate limits, auth), output structure, and differentiation from sibling tools. While the schema covers parameters well, the description does not compensate for the missing annotations and output schema, leaving significant gaps for an agent to understand the tool fully.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the input schema itself. The description does not add any additional meaning or context about the parameters beyond what is already in the schema (e.g., it doesn't explain what 'backlinks and relevant data' includes or how results are structured). With high schema coverage, the baseline score of 3 is appropriate.

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 list of backlinks and relevant data for the specified domain, subdomain, or webpage.' It specifies the verb ('provide'), resource ('backlinks and relevant data'), and target scope ('domain, subdomain, or webpage'). However, it does not explicitly differentiate from sibling tools like 'backlinks_anchors' or 'backlinks_summary,' which prevents a perfect score.

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 many sibling tools in the 'backlinks_' category (e.g., 'backlinks_anchors', 'backlinks_summary', 'backlinks_competitors'), there is no indication of how this tool differs or when it should be preferred. This lack of contextual guidance makes it harder for an agent to select the correct tool.

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/ravinwebsurgeon/seo-mcp'

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