Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_bulk_pages_summary

Analyze comprehensive backlink data for up to 1000 pages, domains, or subdomains to understand link profiles and identify linking opportunities.

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
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
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.

Implementation Reference

  • The main handler function that executes the tool logic by sending a POST request to the DataForSEO backlinks bulk pages summary endpoint and handling the response.
    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 input schema using Zod for the tool parameters: targets (required array of strings) and include_subdomains (optional boolean).
      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)
        };
      }
  • Defines the unique name of the tool used for registration.
    getName(): string {
      return 'backlinks_bulk_pages_summary';
    }
  • Instantiates the BacklinksBulkPagesSummaryTool instance within the tools array.
    new BacklinksBulkPagesSummaryTool(this.dataForSEOClient),
  • Registers all tools, including backlinks_bulk_pages_summary, by mapping their name to definition with bound handler.
    return tools.reduce((acc, tool) => ({
      ...acc,
      [tool.getName()]: {
        description: tool.getDescription(),
        params: tool.getParams(),
        handler: (params: any) => tool.handle(params),
      },
    }), {});
Behavior3/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. It describes key behavioral traits: bulk processing capability (up to 1000 targets), domain limit constraint (no more than 100 different domains), and handling of single vs. multiple targets. However, it does not cover critical aspects like rate limits, authentication requirements, error handling, or response format, leaving gaps for a tool with no annotation coverage.

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 efficiently structured in two sentences: the first states the core purpose and scope, and the second clarifies handling of single targets. Every sentence adds essential information without redundancy, making it front-loaded and appropriately sized for the tool's complexity.

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 the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is partially complete. It covers the purpose, scope, and some constraints but lacks details on behavioral aspects like response format, error conditions, or performance characteristics. Without annotations or output schema, the description should do more to compensate, but it meets a minimum viable level for a read-only summary tool.

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 fully documents both parameters. The description adds value by explaining the tool's purpose and constraints (e.g., bulk of up to 1000 targets, domain limits), which contextualizes the parameters but does not provide additional semantic details beyond the schema. Since there are only 2 parameters and schema coverage is complete, a baseline of 3 is appropriate, with an extra point for the added contextual meaning.

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'), and scope ('bulk of up to 1000'), distinguishing it from sibling tools like 'backlinks_summary' (likely single target) and 'backlinks_bulk_backlinks' (likely detailed list rather than summary).

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 handling single pages, but does not explicitly state when to use this tool versus alternatives like 'backlinks_summary' or 'backlinks_bulk_backlinks'. It provides some operational constraints (e.g., URL format, domain limits) but lacks explicit guidance on tool selection among siblings.

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