Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_summary

Get an overview of backlinks data for any domain, subdomain, or webpage to analyze referring domains and inbound link metrics for SEO assessment.

Instructions

This endpoint will provide you with an overview of backlinks data available for a given domain, subdomain, or webpage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exclude_internal_backlinksNoindicates if internal backlinks from subdomains to the target will be excluded from the results if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results
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
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 main handler function that implements the core logic of the 'backlinks_summary' tool by making an API request to DataForSEO's backlinks summary endpoint.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/summary/live', 'POST', [{
          target: params.target,
          include_subdomains: params.include_subdomains,
          exclude_internal_backlinks: params.exclude_internal_backlinks
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema defining the input parameters for the 'backlinks_summary' tool, including target, include_subdomains, and exclude_internal_backlinks.
      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://)`),
          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),
          exclude_internal_backlinks: z.boolean().optional().describe(`indicates if internal backlinks from subdomains to the target will be excluded from the results
    if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target
    if set to false, internal links will be included in the results`).default(true)
        };
      }
  • Registration of the BacklinksSummaryTool instance within the getTools() method of BacklinksApiModule, mapping it to the 'backlinks_summary' name with its schema and handler.
    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),
        },
      }), {});
    }
  • Import statement for the BacklinksSummaryTool class.
    import { BacklinksSummaryTool } from './tools/backlinks-summary.tool.js';
  • The getName() method that defines the tool's name as 'backlinks_summary'.
    getName(): string {
      return 'backlinks_summary';
    }
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 the tool 'will provide you with an overview' but lacks details on output format (e.g., structured data, summary metrics), pagination, rate limits, authentication needs, or error handling. For a tool with no annotations, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. It directly states what the tool does ('provide an overview of backlinks data') and the target ('domain, subdomain, or webpage'), with zero waste or redundancy.

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 backlinks analysis and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'overview' entails (e.g., summary statistics, aggregated data), potential limitations, or how it differs from detailed sibling tools. For a tool in a crowded namespace with no structured output guidance, more context is needed.

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?

The input schema has 100% description coverage, thoroughly documenting all three parameters. The description adds no parameter-specific information beyond what's in the schema, such as examples or usage tips. According to the rules, with high schema coverage (>80%), the baseline is 3 even without param info in the description.

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 an overview of backlinks data available for a given domain, subdomain, or webpage.' It specifies the verb ('provide') and resource ('backlinks data'), and distinguishes it from siblings by focusing on an 'overview' rather than detailed data like 'backlinks_backlinks' or 'backlinks_anchors.' However, it doesn't explicitly differentiate from all siblings (e.g., 'backlinks_domain_pages_summary'), so it's not a perfect 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 offers no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'backlinks_backlinks' for detailed backlinks, 'backlinks_summary' for overview), it fails to specify scenarios where an overview is preferable, prerequisites, or exclusions. This leaves the agent without context for tool selection.

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