Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_bulk_pages_summary

Analyze backlinks for up to 1000 pages, domains, or subdomains to get comprehensive SEO insights and link profile summaries.

Instructions

This endpoint will provide you with a comprehensive overview of backlinks and related data for a bulk of up to 1000 pages, domains, or subdomains. 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
targetsYesdomains, subdomains or webpages to get summary data 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://) you can specify up to 1000 pages, domains, or subdomains in each request. note that the URLs you set in a single request cannot belong to more than 100 different domains.
include_subdomainsNoindicates if indirect links to the target will be included in the results if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored

Implementation Reference

  • The core handler function that executes the tool logic by sending a POST request to the DataForSEO API endpoint '/v3/backlinks/bulk_pages_summary/live' with the provided targets and include_subdomains parameters.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/bulk_pages_summary/live', 'POST', [{
          targets: params.targets,
          include_subdomains: params.include_subdomains,
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Defines the Zod schema for the tool's input parameters: targets (required array of strings) and optional include_subdomains (boolean, default true).
      getParams(): z.ZodRawShape {
        return {
          targets: z.array(z.string()).describe(`domains, subdomains or webpages to get summary data 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://)
    you can specify up to 1000 pages, domains, or subdomains in each request.
    note that the URLs you set in a single request cannot belong to more than 100 different domains.`),
          include_subdomains: z.boolean().optional().describe(`indicates if indirect links to the target will be included in the results
    if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page
    if set to false, indirect links will be ignored`).default(true)
        };
      }
  • Instantiates and registers the BacklinksBulkPagesSummaryTool in the getTools() method of the BacklinksApiModule, making it available via its getName() 'backlinks_bulk_pages_summary'.
    new BacklinksBulkPagesSummaryTool(this.dataForSEOClient),
  • Defines the tool name as 'backlinks_bulk_pages_summary', used for registration in the module.
    getName(): string {
      return 'backlinks_bulk_pages_summary';
    }
Behavior3/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. It discloses key behavioral traits: bulk processing capability (up to 1000 targets), support for different target types (pages, domains, subdomains), and handling of single targets. However, it does not mention rate limits, authentication needs, error handling, or response format details, leaving gaps for a tool with no annotations.

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 sized with two sentences that are front-loaded with the main purpose. The first sentence covers bulk functionality, and the second clarifies single-target handling. There is no wasted text, but it could be slightly more structured for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is moderately complete. It covers the tool's purpose and basic usage but lacks details on behavioral aspects like rate limits, permissions, or response structure. For a tool with 2 parameters and 100% schema coverage, it meets minimum viability but has clear gaps in transparency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 both parameters thoroughly. The description adds minimal value beyond the schema, mentioning bulk limits and target types, but does not provide additional syntax or format details. With high schema coverage, the baseline is 3, but the description slightly enhances understanding of the 'targets' parameter's purpose, warranting a 4.

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?

The description clearly states the tool's purpose: 'provide you with a comprehensive overview of backlinks and related data for a bulk of up to 1000 pages, domains, or subdomains.' It specifies the verb ('provide'), resource ('backlinks and related data'), scope ('bulk of up to 1000'), and target types ('pages, domains, or subdomains'). It also distinguishes from sibling tools by focusing on bulk summary data rather than detailed backlink listings or other analytics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by mentioning bulk processing (up to 1000 targets) and specifying target types, but it does not explicitly state when to use this tool versus alternatives like 'backlinks_summary' or 'backlinks_domain_pages_summary' from the sibling list. It provides some guidance on single vs. bulk targets but lacks explicit comparisons 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