Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_summary

Analyze backlinks for any domain, subdomain, or webpage to understand link profiles and identify linking opportunities.

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

Implementation Reference

  • The `handle` method executes the tool logic: sends POST request to DataForSEO `/v3/backlinks/summary/live` endpoint with the provided parameters and handles response or error.
    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);
      }
    }
  • Defines the Zod schema for tool input parameters: `target` (required string), `include_subdomains` (optional boolean, default true), `exclude_internal_backlinks` (optional boolean, default true).
      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)
        };
      }
  • The `getName()` method returns the tool name 'backlinks_summary', used for registration.
    getName(): string {
      return 'backlinks_summary';
    }
  • Instantiates the BacklinksSummaryTool in the tools array within `getTools()`.
    new BacklinksSummaryTool(this.dataForSEOClient),
  • The `getTools()` method in BacklinksApiModule registers all backlinks tools, including backlinks_summary, by creating a map keyed by tool name with description, params, and handler wrapper.
    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),
        },
      }), {});
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool provides an 'overview' but doesn't disclose behavioral traits like whether it's a read-only operation, what the output format looks like, if there are rate limits, authentication requirements, or potential costs. For a data-fetching tool with no annotations, this leaves significant gaps in understanding its behavior.

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. It wastes no words and is appropriately sized for a tool with a clear function, making it easy to parse quickly.

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 insufficient. It doesn't explain what an 'overview' entails (e.g., summary statistics, aggregated metrics), how it differs from detailed backlinks tools, or what the agent can expect in return. 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?

Schema description coverage is 100%, so the schema fully documents all three parameters. The description mentions 'domain, subdomain, or webpage' which aligns with the 'target' parameter but adds no additional meaning beyond what's in the schema. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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'), but doesn't explicitly differentiate from sibling tools like 'backlinks_backlinks' or 'backlinks_summary' variants, which likely provide different levels of detail or aggregation.

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 related to backlinks (e.g., 'backlinks_backlinks', 'backlinks_competitors', 'backlinks_timeseries_summary'), there's no indication of what makes this 'overview' distinct or when it's preferred over other backlinks tools.

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