Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_domain_pages

Analyze backlinks for domain pages to identify linking patterns and optimize SEO strategy with detailed page-level data.

Instructions

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

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

Implementation Reference

  • The `handle` method implements the core logic of the 'backlinks_domain_pages' tool by sending a POST request to the DataForSEO '/v3/backlinks/domain_pages/live' endpoint with formatted parameters and handling the response or error.
    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);
      }
    }
  • Defines the input schema using Zod for parameters: 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: 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:
    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 BacklinksApiModule's `getTools()` method instantiates the BacklinksDomainPagesTool and registers it by name along with its description, params, and handler function.
    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),
        },
      }), {});
    }
  • The `getName()` method returns the tool's registered name 'backlinks_domain_pages'.
    getName(): string {
      return 'backlinks_domain_pages';
    }
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 detailed overview,' implying a read-only operation, but doesn't specify data freshness, rate limits, authentication requirements, or pagination behavior. For a tool with 5 parameters and no annotations, this leaves significant gaps in understanding how it behaves.

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, efficient sentence that front-loads the core purpose without unnecessary details. It avoids redundancy and waste, making it appropriately concise. However, it could be slightly improved by structuring to highlight key constraints or usage scenarios, but it's well-sized for its content.

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 of 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., structure of backlink data), potential errors, or performance considerations. For a data retrieval tool with rich filtering options, more context is needed to guide effective use.

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 thoroughly. The description adds no additional meaning beyond what the schema provides, such as clarifying the relationship between parameters or typical use cases. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 returned (backlink data), making the verb+resource relationship explicit. However, it doesn't differentiate from sibling tools like 'backlinks_domain_pages_summary' or 'backlinks_backlinks,' which reduces clarity in context.

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 multiple sibling tools in the 'backlinks' category (e.g., 'backlinks_domain_pages_summary,' 'backlinks_backlinks'), there is no indication of how this tool differs or when it is preferred. Usage is implied only by the purpose statement, lacking explicit context or exclusions.

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