Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_timeseries_summary

Analyze backlink trends for any domain over time by grouping data into daily, weekly, monthly, or yearly intervals to visualize link-building progress.

Instructions

This endpoint will provide you with an overview of backlink data for the target domain available during a period between the two indicated dates. Backlink metrics will be grouped by the time range that you define: day, week, month, or year. Data from this endpoint will be especially helpful for building time-series graphs of daily, weekly, monthly, and yearly link-building progress

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesdomain to get data for required field a domain should be specified without https:// and www. example: "forbes.com"
date_fromNostarting date of the time range optional field this field indicates the date which will be used as a threshold for summary data; minimum value: 2019-01-30 maximum value shouldn’t exceed the date specified in the date_to date format: "yyyy-mm-dd" example: "2021-01-01"
date_toNoending date of the time range optional field if you don’t specify this field, the today’s date will be used by default minimum value shouldn’t preceed the date specified in the date_from maximum value: today’s date date format: "yyyy-mm-dd" example: "2021-01-15"
group_rangeNotime range which will be used to group the results optional field default value: month possible values: day, week, month, year note: for day, we will return items corresponding to all dates between and including date_from and date_to; for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year for example, if you specify: "group_range": "month", "date_from": "2022-03-23", "date_to": "2022-05-13" we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31 if there is no data for a certain day/week/month/year, we will return 0month

Implementation Reference

  • The core handler method that performs the API request to DataForSEO's backlinks timeseries summary endpoint and processes the response.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/timeseries_summary/live', 'POST', [{
          target: params.target,
          date_from: params.date_from,
          date_to: params.date_to,
          group_range: params.group_range
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema definition for the tool's input parameters: target (required), date_from, date_to, group_range.
      getParams(): z.ZodRawShape {
        return {
          target: z.string().describe(`domain to get data for
    required field
    a domain should be specified without https:// and www.
    example:
    "forbes.com"`),
          date_from: z.string().describe(`starting date of the time range
    optional field
    this field indicates the date which will be used as a threshold for summary data;
    minimum value: 2019-01-30
    maximum value shouldn’t exceed the date specified in the date_to
    date format: "yyyy-mm-dd"
    example:
    "2021-01-01"`).optional(),
          date_to: z.string().describe(`ending date of the time range
    optional field
    if you don’t specify this field, the today’s date will be used by default
    minimum value shouldn’t preceed the date specified in the date_from
    maximum value: today’s date
    date format: "yyyy-mm-dd"
    example:
    "2021-01-15"`).optional(),
            group_range: z.string().optional().describe(`time range which will be used to group the results
    optional field
    default value: month
    possible values: day, week, month, year
    note: for day, we will return items corresponding to all dates between and including date_from and date_to;
    for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year
    
    for example, if you specify:
    "group_range": "month",
    "date_from": "2022-03-23",
    "date_to": "2022-05-13"
    we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31
    
    if there is no data for a certain day/week/month/year, we will return 0`).default('month')
        };
      }
  • The BacklinksTimeseriesSummaryTool is instantiated and registered in the getTools() method of BacklinksApiModule, added to the tools array and mapped to its name with description, params, 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 BacklinksTimeseriesSummaryTool class.
    import { BacklinksTimeseriesSummaryTool } from './tools/backlinks-timeseries-summary.tool.js';
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. It mentions grouping behavior and that 'if there is no data for a certain day/week/month/year, we will return 0,' which adds useful context. However, it doesn't disclose critical behavioral traits such as rate limits, authentication needs, data freshness, error handling, or pagination. For a data retrieval tool with no annotation coverage, this leaves significant gaps.

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 core functionality. The first sentence covers purpose and key parameters, while the second adds usage context. There's no redundant information, though 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 the tool's complexity (time-series data with grouping), no annotations, and no output schema, the description is moderately complete. It explains the grouping logic and data gaps, but lacks details on output format, error cases, or performance considerations. It's adequate for basic use but has clear gaps for advanced scenarios.

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 four parameters thoroughly. The description adds minimal value beyond the schema, only implying the grouping functionality without providing additional syntax or format details. Baseline 3 is appropriate when the schema does the heavy lifting.

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 backlink data for the target domain available during a period between the two indicated dates' and specifies that metrics are 'grouped by the time range that you define.' It distinguishes from siblings by focusing on time-series summary rather than other backlink analyses like anchors, competitors, or summary. However, it doesn't explicitly contrast with 'backlinks_timeseries_new_lost_summary' which appears to be a close sibling.

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 stating 'Data from this endpoint will be especially helpful for building time-series graphs of daily, weekly, monthly, and yearly link-building progress,' which suggests when to use it. However, it lacks explicit guidance on when to choose this tool over alternatives like 'backlinks_summary' or 'backlinks_timeseries_new_lost_summary,' and doesn't mention prerequisites 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