Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_domain_pages

Analyze domain pages with backlink data to identify which pages attract the most links, filter results by specific criteria, and understand link distribution across your website.

Instructions

This endpoint will provide you with a detailed overview of domain pages with backlink data for each page

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: regex, not_regex, =, <>, in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: ["meta.internal_links_count",">","1"] [["meta.external_links_count",">","2"], "and", ["backlinks",">","10"]] [["first_visited",">","2017-10-23 11:31:45 +00:00"], "and", [["title","like","%seo%"],"or",["referring_domains",">","10"]]]
limitNothe maximum number of returned pages
offsetNooffset in the results array of returned pages optional field default value: 0 if you specify the 10 value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages
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: ["page_summary.backlinks,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: ["page_summary.backlinks,desc","page_summary.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://)

Implementation Reference

  • The handle method implements the core logic of the backlinks_domain_pages tool by constructing and sending a POST request to the DataForSEO API endpoint '/v3/backlinks/domain_pages/live' with the provided parameters, then validating and formatting the response or handling errors.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/domain_pages/live', 'POST', [{
          target: params.target,
          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 validating input parameters including target (required), 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://)`),
          limit: z.number().min(1).max(1000).default(10).optional().describe("the maximum number of returned pages"),
          offset: z.number().min(0).optional().describe(
            `offset in the results array of returned pages
    optional field
    default value: 0
    if you specify the 10 value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages`
          ),
          filters: this.getFilterExpression().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:
    regex, not_regex, =, <>, in, not_in, like, not_like, ilike, not_ilike, match, not_match
    you can use the % operator with like and not_like to match any string of zero or more characters
    example:
    ["meta.internal_links_count",">","1"]
    [["meta.external_links_count",">","2"],
    "and",
    ["backlinks",">","10"]]
    
    [["first_visited",">","2017-10-23 11:31:45 +00:00"],
    "and",
    [["title","like","%seo%"],"or",["referring_domains",">","10"]]]`
          ),
          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:
    ["page_summary.backlinks,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:
    ["page_summary.backlinks,desc","page_summary.rank,asc"]`
          ),
        };
      }
  • The BacklinksDomainPagesTool is instantiated in the tools array returned by BacklinksApiModule's getTools() method, where it is registered into a record keyed by its name 'backlinks_domain_pages' with description, params, and wrapped handler.
    new BacklinksDomainPagesTool(this.dataForSEOClient),
  • Import statement for the BacklinksDomainPagesTool class used in the module.
    import { BacklinksDomainPagesTool } from './tools/backlinks-domain-pages.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 providing a 'detailed overview' but doesn't specify what that includes (e.g., pagination, rate limits, authentication needs, data freshness, or error handling). For a tool with 5 parameters and no output schema, this lack of detail is a significant gap, making it inadequate for informed use.

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, clear sentence that efficiently states the tool's purpose without unnecessary words. It's front-loaded and easy to parse, though it could be slightly more structured (e.g., by including key usage notes). Overall, it's concise and well-formed, earning a high score.

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, no annotations, no output schema, and many sibling tools), the description is incomplete. It lacks behavioral details, usage guidelines, and output information, which are crucial for an agent to use the tool effectively. The high schema coverage helps, but the description doesn't fill the gaps in context, making it insufficient for a tool of this nature.

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%, meaning the input schema already documents all parameters thoroughly. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain how 'target' relates to 'filters' or typical use cases). With high schema coverage, the baseline is 3, as the description doesn't compensate or add value beyond the structured data.

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 domain pages with backlink data for each page.' It specifies the resource (domain pages) and the data (backlink data), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'backlinks_domain_pages_summary' or 'backlinks_backlinks,' which might offer similar data, so it doesn't reach a 5.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'backlinks_domain_pages_summary,' 'backlinks_backlinks'), there's no indication of context, prerequisites, or exclusions. This leaves the agent guessing about the appropriate use case, resulting in a low score.

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