Skip to main content
Glama

AIsa Backlinks

by one.aisa
OverviewDiscussionsAdmin

New & Lost Backlinks Timeseries Summary

post_dataforseo_backlinks_timeseries_new_lost_live
Destructive

‌ This endpoint will provide you with the number of new and lost backlinks and referring domains for the domain specified in the target field.

Usage-based billing; Default request estimate: $0.0372 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
bodyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / body / items / oneOf
      Previous value: -[
-  {
-    "example": [
-      {
-        "date_from": "2021-12-01",
-        "date_to": "2022-02-01",
-        "group_range": "month",
-        "target": "dataforseo.com"
-      }
-    ],
-    "properties": {
-      "date_from": {
-        "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "date_to": {
-        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "group_range": {
-        "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain  <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "include_subdomains": {
-        "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>",
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "tag": {
-        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "target": {
-        "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "group_range": {
+        "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain  <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "include_subdomains": {
+        "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "target": {
+        "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
  2. Changed2 schema fields changed
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "date_from": "2021-12-01",
-        "date_to": "2022-02-01",
-        "group_range": "month",
-        "target": "dataforseo.com"
-      }
-    ],
-    "properties": {
-      "date_from": {
-        "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "date_to": {
-        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "group_range": {
-        "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain  <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "include_subdomains": {
-        "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>",
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "tag": {
-        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "target": {
-        "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / body / items / oneOf
      Added value: +[
+  {
+    "example": [
+      {
+        "date_from": "2021-12-01",
+        "date_to": "2022-02-01",
+        "group_range": "month",
+        "target": "dataforseo.com"
+      }
+    ],
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "group_range": {
+        "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain  <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "include_subdomains": {
+        "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "target": {
+        "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
  3. Changed7 schema fields changed
    • addedInput schema / properties / body / example
      Added value: +[
+  {
+    "date_from": "2021-12-01",
+    "date_to": "2022-02-01",
+    "group_range": "month",
+    "target": "dataforseo.com"
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "date_from": "2021-12-01",
+        "date_to": "2022-02-01",
+        "group_range": "month",
+        "target": "dataforseo.com"
+      }
+    ],
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "group_range": {
+        "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain  <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "include_subdomains": {
+        "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "target": {
+        "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / properties
      Removed value: -{
-  "date_from": {
-    "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains; the backlinks and referring domains that appeared in our index after the specified date will be considered as new; the backlinks and referring domains that weren’t found after the specified date, but were present before, will be considered as lost; 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\"",
-    "type": "string"
-  },
-  "date_to": {
-    "description": "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\"",
-    "type": "string"
-  },
-  "group_range": {
-    "description": "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",
-    "type": "string"
-  },
-  "include_subdomains": {
-    "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true",
-    "type": "boolean"
-  },
-  "tag": {
-    "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response",
-    "type": "string"
-  },
-  "target": {
-    "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "target"
-]
    • changedInput schema / properties / body / items / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "body"
-]New value: +[]
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed7 schema fields changed
    • removedInput schema / properties / body / example
      Removed value: -[
-  {
-    "date_from": "2021-12-01",
-    "date_to": "2022-02-01",
-    "group_range": "month",
-    "target": "dataforseo.com"
-  }
-]
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "date_from": "2021-12-01",
-        "date_to": "2022-02-01",
-        "group_range": "month",
-        "target": "dataforseo.com"
-      }
-    ],
-    "properties": {
-      "date_from": {
-        "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "date_to": {
-        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "group_range": {
-        "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain  <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "include_subdomains": {
-        "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>",
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "tag": {
-        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "target": {
-        "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / body / items / properties
      Added value: +{
+  "date_from": {
+    "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains; the backlinks and referring domains that appeared in our index after the specified date will be considered as new; the backlinks and referring domains that weren’t found after the specified date, but were present before, will be considered as lost; 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\"",
+    "type": "string"
+  },
+  "date_to": {
+    "description": "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\"",
+    "type": "string"
+  },
+  "group_range": {
+    "description": "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",
+    "type": "string"
+  },
+  "include_subdomains": {
+    "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true",
+    "type": "boolean"
+  },
+  "tag": {
+    "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response",
+    "type": "string"
+  },
+  "target": {
+    "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / items / required
      Added value: +[
+  "target"
+]
    • changedInput schema / properties / body / items / type
      Previous value: -[
-  "object",
-  "null"
-]New value: +"object"
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "body"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  5. Changed7 schema fields changed
    • addedInput schema / properties / body / example
      Added value: +[
+  {
+    "date_from": "2021-12-01",
+    "date_to": "2022-02-01",
+    "group_range": "month",
+    "target": "dataforseo.com"
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "date_from": "2021-12-01",
+        "date_to": "2022-02-01",
+        "group_range": "month",
+        "target": "dataforseo.com"
+      }
+    ],
+    "properties": {
+      "date_from": {
+        "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_to": {
+        "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "group_range": {
+        "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain  <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "include_subdomains": {
+        "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "tag": {
+        "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "target": {
+        "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / properties
      Removed value: -{
-  "date_from": {
-    "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains; the backlinks and referring domains that appeared in our index after the specified date will be considered as new; the backlinks and referring domains that weren’t found after the specified date, but were present before, will be considered as lost; 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\"",
-    "type": "string"
-  },
-  "date_to": {
-    "description": "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\"",
-    "type": "string"
-  },
-  "group_range": {
-    "description": "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",
-    "type": "string"
-  },
-  "include_subdomains": {
-    "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true",
-    "type": "boolean"
-  },
-  "tag": {
-    "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response",
-    "type": "string"
-  },
-  "target": {
-    "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "target"
-]
    • changedInput schema / properties / body / items / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "body"
-]New value: +[]
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  6. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), yet the description adds no behavioral context of its own — no mention of auth, rate limits, credit consumption beyond the generic pricing boilerplate, or what the response contains. Notably, the text reads as a pure data-retrieval operation while the annotations declare it destructive and non-read-only, a tension the description never clarifies.

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?

One focused sentence front-loads the purpose, followed by a pricing block. The core sentence is tight and wastes nothing, though the injected billing boilerplate is non-informative noise that dilutes the definition slightly.

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?

An output schema exists, so return-value details need not be spelled out, and the nested parameter descriptions cover the inputs. What is missing is selection guidance against the large family of sibling backlink tools and any behavioral clarification relative to the surprisingly destructive annotations, leaving the definition only adequate for a tool in such a crowded namespace.

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 only points at one field ('the domain specified in the target field') and explains nothing about date_from, date_to, group_range, or include_subdomains. However, the input schema itself carries rich per-field descriptions for those nested parameters, so the structured data does most of the work and the description's contribution is marginal.

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 states a specific verb+resource: it returns counts of new and lost backlinks and referring domains for a target domain. That is clear and concrete. It does not, however, distinguish this tool from close siblings such as post_dataforseo_backlinks_bulk_new_lost_backlinks_live or post_dataforseo_backlinks_timeseries_summary_live, so an agent cannot easily tell which new/lost variant to pick.

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 text only says what the endpoint returns; it gives no when-to-use guidance, no when-not-to-use, and never names an alternative sibling. With many overlapping backlink endpoints available, a routing hint (e.g. use this vs. the bulk new/lost or timeseries_summary variants) is missing entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AIsa Backlinks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources