Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_timeseries_summary

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

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
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
targetYesdomain to get data for required field a domain should be specified without https:// and www. example: "forbes.com"

Implementation Reference

  • The handle method executes the tool logic: makes a POST request to DataForSEO /v3/backlinks/timeseries_summary/live endpoint with provided parameters and handles response/error.
    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);
      }
    }
  • Defines Zod schema for input parameters: target (required domain), date_from/date_to (optional dates), group_range (optional, default 'month').
      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')
        };
      }
  • Instantiates BacklinksTimeseriesSummaryTool within the tools array of BacklinksApiModule's getTools() method, effectively registering the tool with its handler wrapped.
    new BacklinksTimeseriesSummaryTool(this.dataForSEOClient),
  • Imports the BacklinksTimeseriesSummaryTool class required for registration.
    import { BacklinksTimeseriesSummaryTool } from './tools/backlinks-timeseries-summary.tool.js';
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 the grouping behavior and handling of missing data ('if there is no data for a certain day/week/month/year, we will return 0'), which is valuable. However, it doesn't mention rate limits, authentication requirements, whether this is a read-only operation, or what the output format looks like (though there's no output schema). The description adds some behavioral context but 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 two sentences that efficiently convey the core functionality and usage context. The first sentence states the purpose and key parameters, while the second highlights the primary use case. There's no redundant information, and it's appropriately sized for a tool with well-documented parameters in the schema.

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 complexity (time-series analysis with grouping), no annotations, and no output schema, the description is moderately complete. It explains the grouping behavior and missing data handling, which is crucial. However, it doesn't cover authentication, rate limits, error conditions, or the structure of returned data (e.g., what metrics are included in the 'overview'). For a tool with no annotations or output schema, more behavioral and output details would be needed for higher completeness.

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 description mentions grouping by time range (day, week, month, year) and the purpose of building time-series graphs, which adds context beyond the input schema. However, with 100% schema description coverage, the schema already thoroughly documents all 4 parameters (date_from, date_to, group_range, target) with examples, constraints, and defaults. The description provides marginal additional meaning, so the baseline 3 is appropriate.

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 mentions grouping by time range. It specifies the resource (backlink data for a domain) and action (overview/time-series summary). However, it doesn't explicitly differentiate from sibling tools like 'backlinks_summary' or 'backlinks_timeseries_new_lost_summary', which would require a 5.

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.' This suggests when to use it (for time-series visualization), but it doesn't provide explicit guidance on when to choose this tool over alternatives like 'backlinks_summary' or 'backlinks_timeseries_new_lost_summary', nor does it mention any 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/cortex8/oyt-dataforseo-mcp-worker'

If you have feedback or need assistance with the MCP directory API, please join our Discord server