Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_domain_pages_summary

Analyze backlink profiles for domains or specific pages to identify referring domains, anchor text, and link metrics for SEO assessment.

Instructions

This endpoint will provide you with detailed summary data on all backlinks and related metrics for each page of the target domain or subdomain you specify. If you indicate a single page as a target, you will get comprehensive summary data on all backlinks for that 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 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
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: ["referring_links_types.anchors",">","1"] [["broken_pages",">","2"], "and", ["backlinks",">","10"]] [["first_seen",">","2017-10-23 11:31:45 +00:00"], "and", [["anchor","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: ["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: ["backlinks,desc","rank,asc"]

Implementation Reference

  • The handler function that implements the core logic of the tool by sending a POST request to the DataForSEO API endpoint '/v3/backlinks/domain_pages_summary/live' with formatted parameters and handling the response.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/domain_pages_summary/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, specifying parameters such as target (required), limit, offset, filters, and order_by with detailed descriptions and constraints.
      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 anchors"),
          offset: z.number().min(0).optional().describe(
            `offset 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`
          ),
          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:
    ["referring_links_types.anchors",">","1"]
    [["broken_pages",">","2"],
    "and",
    ["backlinks",">","10"]]
    
    [["first_seen",">","2017-10-23 11:31:45 +00:00"],
    "and",
    [["anchor","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:
    ["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:
    ["backlinks,desc","rank,asc"]`
          ),
        };
      }
  • Registers the tool by instantiating BacklinksDomainPagesSummaryTool in the getTools() method's tools array, which is used to expose the tool with its name, description, params, and handler.
    new BacklinksDomainPagesSummaryTool(this.dataForSEOClient),
  • Imports the BacklinksDomainPagesSummaryTool class necessary for its registration in the module.
    import { BacklinksDomainPagesSummaryTool } from './tools/backlinks-domain-pages-summary.tool.js';
  • Defines the tool's name as 'backlinks_domain_pages_summary', which is used for registration and invocation.
    getName(): string {
      return 'backlinks_domain_pages_summary';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the tool provides 'detailed summary data' and handles both domains and single pages, it fails to disclose critical behavioral traits: whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior (beyond the limit/offset parameters), or what format the 'summary data' returns. For a tool with 5 parameters and complex filtering capabilities, this is a significant gap.

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 appropriately concise—two sentences that directly state the tool's core functionality. It's front-loaded with the main purpose and efficiently covers the domain vs. page distinction. No wasted words or redundant information, though it could benefit from more structured guidance.

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 tool's complexity (5 parameters with rich filtering/sorting capabilities) and lack of both annotations and output schema, the description is insufficient. It doesn't explain what 'detailed summary data' includes, how results are structured, whether operations are idempotent, or any error conditions. For a data retrieval tool with pagination and filtering, users need more context about output format and behavioral constraints.

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 parameter semantics beyond what's in the schema—it doesn't clarify the 'target' parameter's format beyond what the schema says, nor does it explain how 'filters' or 'order_by' interact with the summary output. With complete 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 detailed summary data on all backlinks and related metrics for each page of the target domain or subdomain.' It specifies the verb ('provide'), resource ('backlinks and related metrics'), and scope ('domain, subdomain, or webpage'). However, it doesn't explicitly differentiate from sibling tools like 'backlinks_summary' or 'backlinks_domain_pages', which might offer similar functionality.

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 minimal usage guidance. It explains what happens when you specify a domain vs. a single page, but offers no advice on when to use this tool versus alternatives like 'backlinks_summary' or 'backlinks_domain_pages' from the sibling list. There's no mention of prerequisites, typical use cases, or performance considerations.

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