Skip to main content
Glama

AIsa On-Page Audit

by one.aisa
OverviewDiscussionsAdmin

OnPage API Resources

post_dataforseo_on_page_resources
Destructive

‌‌ This endpoint will provide you with a list of resources, including images, scripts, stylesheets, and broken elements. You will get a detailed overview of every resource found on the crawled pages.

Usage-based billing; Default request estimate: $0.012 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. Changed3 schema fields changed
    • addedInput schema / $defs
      Added value: +{
+  "Provider0A3E90081762_AisaDataforseoFilterJsonValue": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
+        },
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
+        },
+        "type": "array"
+      }
+    ],
+    "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator."
+  }
+}
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "properties": {
+      "filters": {
+        "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"resource_type\",\"=\",\"stylesheet\"]</code><p><code>[[\"resource_type\",\"=\",\"image\"],<br>\"and\",[\"checks.is_https\",\"=\",false]]</code><p><code>[[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\"&gt;\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">by this link.</a>",
+        "items": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "number"
+            },
+            {
+              "type": "boolean"
+            },
+            {
+              "additionalProperties": {
+                "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
+              },
+              "type": [
+                "object",
+                "null"
+              ]
+            },
+            {
+              "items": {
+                "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
+              },
+              "type": "array"
+            }
+          ],
+          "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator."
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "<em>ID of the task</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\">Task POST</a> endpoint<br>example:<br>\"07131248-1535-0216-1000-17384017ad04\"",
+        "type": "string"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned resources</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "offset": {
+        "description": "<em>offset in the results array of returned resources</em><br>optional field<br>default value: <code>0</code><br>maximum value: <code>2000000</code><br>if you specify the <code>10</code> value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "order_by": {
+        "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"size,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"size,desc\",\"fetch_timing.fetch_end,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "relevant_pages_filters": {
+        "description": "<em>filter the resources by relevant pages</em><br>optional field<br>you can use this field to obtain resources from pages matching to the defined parameters<br>you can apply the same filters here as available for the <a href=\"/v3/on_page/pages/\" rel=\"noopener noreferrer\" target=\"_blank\">pages endpoint</a><br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"checks.no_image_title\",\"=\",true]</code>",
+        "items": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "number"
+            },
+            {
+              "type": "boolean"
+            },
+            {
+              "additionalProperties": {
+                "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
+              },
+              "type": [
+                "object",
+                "null"
+              ]
+            },
+            {
+              "items": {
+                "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
+              },
+              "type": "array"
+            }
+          ],
+          "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator."
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "search_after_token": {
+        "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request",
+        "type": [
+          "string",
+          "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"
+        ]
+      },
+      "url": {
+        "description": "<em>page URL</em><br>optional field<br>specify this field if you want to get the resources for a specific page<br>note that to obtain resource's <code>meta</code> from a particular URL, you should specify the URL in this field;<br>if you do not indicate a <code>url</code> when setting a task, resource's <code>meta</code> in the results will be returned based on the data from the page where our crawler first saw the resource",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / oneOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "filters": [
-          [
-            "resource_type",
-            "=",
-            "image"
-          ],
-          "and",
-          [
-            "size",
-            ">",
-            100000
-          ]
-        ],
-        "id": "07281559-0695-0216-0000-c269be8b7592",
-        "limit": 10,
-        "order_by": [
-          "size,desc"
-        ]
-      }
-    ],
-    "properties": {
-      "filters": {
-        "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"resource_type\",\"=\",\"stylesheet\"]</code><p><code>[[\"resource_type\",\"=\",\"image\"],<br>\"and\",[\"checks.is_https\",\"=\",false]]</code><p><code>[[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\"&gt;\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">by this link.</a>",
-        "items": {
-          "type": [
-            "object",
-            "null"
-          ]
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "<em>ID of the task</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\">Task POST</a> endpoint<br>example:<br>\"07131248-1535-0216-1000-17384017ad04\"",
-        "type": "string"
-      },
-      "limit": {
-        "description": "<em>the maximum number of returned resources</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "offset": {
-        "description": "<em>offset in the results array of returned resources</em><br>optional field<br>default value: <code>0</code><br>maximum value: <code>2000000</code><br>if you specify the <code>10</code> value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "order_by": {
-        "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"size,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"size,desc\",\"fetch_timing.fetch_end,desc\"]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "relevant_pages_filters": {
-        "description": "<em>filter the resources by relevant pages</em><br>optional field<br>you can use this field to obtain resources from pages matching to the defined parameters<br>you can apply the same filters here as available for the <a href=\"/v3/on_page/pages/\" rel=\"noopener noreferrer\" target=\"_blank\">pages endpoint</a><br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"checks.no_image_title\",\"=\",true]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "search_after_token": {
-        "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request",
-        "type": [
-          "string",
-          "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"
-        ]
-      },
-      "url": {
-        "description": "<em>page URL</em><br>optional field<br>specify this field if you want to get the resources for a specific page<br>note that to obtain resource's <code>meta</code> from a particular URL, you should specify the URL in this field;<br>if you do not indicate a <code>url</code> when setting a task, resource's <code>meta</code> in the results will be returned based on the data from the page where our crawler first saw the resource",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-]
  2. Changed2 schema fields changed
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "filters": [
-          [
-            "resource_type",
-            "=",
-            "image"
-          ],
-          "and",
-          [
-            "size",
-            ">",
-            100000
-          ]
-        ],
-        "id": "07281559-0695-0216-0000-c269be8b7592",
-        "limit": 10,
-        "order_by": [
-          "size,desc"
-        ]
-      }
-    ],
-    "properties": {
-      "filters": {
-        "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"resource_type\",\"=\",\"stylesheet\"]</code><p><code>[[\"resource_type\",\"=\",\"image\"],<br>\"and\",[\"checks.is_https\",\"=\",false]]</code><p><code>[[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\"&gt;\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">by this link.</a>",
-        "items": {
-          "type": [
-            "object",
-            "null"
-          ]
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "<em>ID of the task</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\">Task POST</a> endpoint<br>example:<br>\"07131248-1535-0216-1000-17384017ad04\"",
-        "type": "string"
-      },
-      "limit": {
-        "description": "<em>the maximum number of returned resources</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "offset": {
-        "description": "<em>offset in the results array of returned resources</em><br>optional field<br>default value: <code>0</code><br>maximum value: <code>2000000</code><br>if you specify the <code>10</code> value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "order_by": {
-        "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"size,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"size,desc\",\"fetch_timing.fetch_end,desc\"]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "relevant_pages_filters": {
-        "description": "<em>filter the resources by relevant pages</em><br>optional field<br>you can use this field to obtain resources from pages matching to the defined parameters<br>you can apply the same filters here as available for the <a href=\"/v3/on_page/pages/\" rel=\"noopener noreferrer\" target=\"_blank\">pages endpoint</a><br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"checks.no_image_title\",\"=\",true]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "search_after_token": {
-        "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request",
-        "type": [
-          "string",
-          "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"
-        ]
-      },
-      "url": {
-        "description": "<em>page URL</em><br>optional field<br>specify this field if you want to get the resources for a specific page<br>note that to obtain resource's <code>meta</code> from a particular URL, you should specify the URL in this field;<br>if you do not indicate a <code>url</code> when setting a task, resource's <code>meta</code> in the results will be returned based on the data from the page where our crawler first saw the resource",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / body / items / oneOf
      Added value: +[
+  {
+    "example": [
+      {
+        "filters": [
+          [
+            "resource_type",
+            "=",
+            "image"
+          ],
+          "and",
+          [
+            "size",
+            ">",
+            100000
+          ]
+        ],
+        "id": "07281559-0695-0216-0000-c269be8b7592",
+        "limit": 10,
+        "order_by": [
+          "size,desc"
+        ]
+      }
+    ],
+    "properties": {
+      "filters": {
+        "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"resource_type\",\"=\",\"stylesheet\"]</code><p><code>[[\"resource_type\",\"=\",\"image\"],<br>\"and\",[\"checks.is_https\",\"=\",false]]</code><p><code>[[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\"&gt;\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">by this link.</a>",
+        "items": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "<em>ID of the task</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\">Task POST</a> endpoint<br>example:<br>\"07131248-1535-0216-1000-17384017ad04\"",
+        "type": "string"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned resources</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "offset": {
+        "description": "<em>offset in the results array of returned resources</em><br>optional field<br>default value: <code>0</code><br>maximum value: <code>2000000</code><br>if you specify the <code>10</code> value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "order_by": {
+        "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"size,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"size,desc\",\"fetch_timing.fetch_end,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "relevant_pages_filters": {
+        "description": "<em>filter the resources by relevant pages</em><br>optional field<br>you can use this field to obtain resources from pages matching to the defined parameters<br>you can apply the same filters here as available for the <a href=\"/v3/on_page/pages/\" rel=\"noopener noreferrer\" target=\"_blank\">pages endpoint</a><br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"checks.no_image_title\",\"=\",true]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "search_after_token": {
+        "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request",
+        "type": [
+          "string",
+          "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"
+        ]
+      },
+      "url": {
+        "description": "<em>page URL</em><br>optional field<br>specify this field if you want to get the resources for a specific page<br>note that to obtain resource's <code>meta</code> from a particular URL, you should specify the URL in this field;<br>if you do not indicate a <code>url</code> when setting a task, resource's <code>meta</code> in the results will be returned based on the data from the page where our crawler first saw the resource",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+]
  3. Changed7 schema fields changed
    • addedInput schema / properties / body / example
      Added value: +[
+  {
+    "filters": [
+      [
+        "resource_type",
+        "=",
+        "image"
+      ],
+      "and",
+      [
+        "size",
+        ">",
+        100000
+      ]
+    ],
+    "id": "07281559-0695-0216-0000-c269be8b7592",
+    "limit": 10,
+    "order_by": [
+      "size,desc"
+    ]
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "filters": [
+          [
+            "resource_type",
+            "=",
+            "image"
+          ],
+          "and",
+          [
+            "size",
+            ">",
+            100000
+          ]
+        ],
+        "id": "07281559-0695-0216-0000-c269be8b7592",
+        "limit": 10,
+        "order_by": [
+          "size,desc"
+        ]
+      }
+    ],
+    "properties": {
+      "filters": {
+        "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"resource_type\",\"=\",\"stylesheet\"]</code><p><code>[[\"resource_type\",\"=\",\"image\"],<br>\"and\",[\"checks.is_https\",\"=\",false]]</code><p><code>[[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\"&gt;\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">by this link.</a>",
+        "items": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "<em>ID of the task</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\">Task POST</a> endpoint<br>example:<br>\"07131248-1535-0216-1000-17384017ad04\"",
+        "type": "string"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned resources</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "offset": {
+        "description": "<em>offset in the results array of returned resources</em><br>optional field<br>default value: <code>0</code><br>maximum value: <code>2000000</code><br>if you specify the <code>10</code> value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "order_by": {
+        "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"size,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"size,desc\",\"fetch_timing.fetch_end,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "relevant_pages_filters": {
+        "description": "<em>filter the resources by relevant pages</em><br>optional field<br>you can use this field to obtain resources from pages matching to the defined parameters<br>you can apply the same filters here as available for the <a href=\"/v3/on_page/pages/\" rel=\"noopener noreferrer\" target=\"_blank\">pages endpoint</a><br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"checks.no_image_title\",\"=\",true]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "search_after_token": {
+        "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request",
+        "type": [
+          "string",
+          "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"
+        ]
+      },
+      "url": {
+        "description": "<em>page URL</em><br>optional field<br>specify this field if you want to get the resources for a specific page<br>note that to obtain resource's <code>meta</code> from a particular URL, you should specify the URL in this field;<br>if you do not indicate a <code>url</code> when setting a task, resource's <code>meta</code> in the results will be returned based on the data from the page where our crawler first saw the resource",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / properties
      Removed value: -{
-  "filters": {
-    "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, , , >, >=, =, , in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: [\"resource_type\",\"=\",\"stylesheet\"] [[\"resource_type\",\"=\",\"image\"], \"and\",[\"checks.is_https\",\"=\",false]] [[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\">\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]] The full list of possible filters is available by this link.",
-    "items": {},
-    "type": "array"
-  },
-  "id": {
-    "description": "ID of the task required field you can get this ID in the response of the Task POST endpoint example: “07131248-1535-0216-1000-17384017ad04”",
-    "type": "string"
-  },
-  "limit": {
-    "description": "the maximum number of returned resources optional field default value: 100 maximum value: 1000",
-    "type": "integer"
-  },
-  "offset": {
-    "description": "offset in the results array of returned resources optional field default value: 0 maximum value: 2000000 if you specify the 10 value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
-    "type": "integer"
-  },
-  "order_by": {
-    "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"size,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"size,desc\",\"fetch_timing.fetch_end,desc\"]",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "relevant_pages_filters": {
-    "description": "filter the resources by relevant pages optional field you can use this field to obtain resources from pages matching to the defined parameters you can apply the same filters here as available for the pages endpoint you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, , , >, >=, =, , in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: [\"checks.no_image_title\",\"=\",true]",
-    "items": {},
-    "type": "array"
-  },
-  "search_after_token": {
-    "description": "token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 20,000 results in a single request; by specifying the unique search_after_token value from the response array, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task ; Note: if the search_after_token is specified in the request, all other parameters should be identical to the previous request",
-    "type": "string"
-  },
-  "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"
-  },
-  "url": {
-    "description": "page URL optional field specify this field if you want to get the resources for a specific page note that to obtain resource’s meta from a particular URL, you should specify the URL in this field; if you do not indicate a url when setting a task, resource’s meta in the results will be returned based on the data from the page where our crawler first saw the resource",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "id"
-]
    • 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: -[
-  {
-    "filters": [
-      [
-        "resource_type",
-        "=",
-        "image"
-      ],
-      "and",
-      [
-        "size",
-        ">",
-        100000
-      ]
-    ],
-    "id": "07281559-0695-0216-0000-c269be8b7592",
-    "limit": 10,
-    "order_by": [
-      "size,desc"
-    ]
-  }
-]
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "filters": [
-          [
-            "resource_type",
-            "=",
-            "image"
-          ],
-          "and",
-          [
-            "size",
-            ">",
-            100000
-          ]
-        ],
-        "id": "07281559-0695-0216-0000-c269be8b7592",
-        "limit": 10,
-        "order_by": [
-          "size,desc"
-        ]
-      }
-    ],
-    "properties": {
-      "filters": {
-        "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"resource_type\",\"=\",\"stylesheet\"]</code><p><code>[[\"resource_type\",\"=\",\"image\"],<br>\"and\",[\"checks.is_https\",\"=\",false]]</code><p><code>[[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\"&gt;\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">by this link.</a>",
-        "items": {
-          "type": [
-            "object",
-            "null"
-          ]
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "<em>ID of the task</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\">Task POST</a> endpoint<br>example:<br>\"07131248-1535-0216-1000-17384017ad04\"",
-        "type": "string"
-      },
-      "limit": {
-        "description": "<em>the maximum number of returned resources</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "offset": {
-        "description": "<em>offset in the results array of returned resources</em><br>optional field<br>default value: <code>0</code><br>maximum value: <code>2000000</code><br>if you specify the <code>10</code> value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "order_by": {
-        "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"size,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"size,desc\",\"fetch_timing.fetch_end,desc\"]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "relevant_pages_filters": {
-        "description": "<em>filter the resources by relevant pages</em><br>optional field<br>you can use this field to obtain resources from pages matching to the defined parameters<br>you can apply the same filters here as available for the <a href=\"/v3/on_page/pages/\" rel=\"noopener noreferrer\" target=\"_blank\">pages endpoint</a><br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"checks.no_image_title\",\"=\",true]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "null"
-        ]
-      },
-      "search_after_token": {
-        "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request",
-        "type": [
-          "string",
-          "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"
-        ]
-      },
-      "url": {
-        "description": "<em>page URL</em><br>optional field<br>specify this field if you want to get the resources for a specific page<br>note that to obtain resource's <code>meta</code> from a particular URL, you should specify the URL in this field;<br>if you do not indicate a <code>url</code> when setting a task, resource's <code>meta</code> in the results will be returned based on the data from the page where our crawler first saw the resource",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / body / items / properties
      Added value: +{
+  "filters": {
+    "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, , , >, >=, =, , in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: [\"resource_type\",\"=\",\"stylesheet\"] [[\"resource_type\",\"=\",\"image\"], \"and\",[\"checks.is_https\",\"=\",false]] [[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\">\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]] The full list of possible filters is available by this link.",
+    "items": {},
+    "type": "array"
+  },
+  "id": {
+    "description": "ID of the task required field you can get this ID in the response of the Task POST endpoint example: “07131248-1535-0216-1000-17384017ad04”",
+    "type": "string"
+  },
+  "limit": {
+    "description": "the maximum number of returned resources optional field default value: 100 maximum value: 1000",
+    "type": "integer"
+  },
+  "offset": {
+    "description": "offset in the results array of returned resources optional field default value: 0 maximum value: 2000000 if you specify the 10 value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
+    "type": "integer"
+  },
+  "order_by": {
+    "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"size,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"size,desc\",\"fetch_timing.fetch_end,desc\"]",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "relevant_pages_filters": {
+    "description": "filter the resources by relevant pages optional field you can use this field to obtain resources from pages matching to the defined parameters you can apply the same filters here as available for the pages endpoint you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, , , >, >=, =, , in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: [\"checks.no_image_title\",\"=\",true]",
+    "items": {},
+    "type": "array"
+  },
+  "search_after_token": {
+    "description": "token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 20,000 results in a single request; by specifying the unique search_after_token value from the response array, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task ; Note: if the search_after_token is specified in the request, all other parameters should be identical to the previous request",
+    "type": "string"
+  },
+  "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"
+  },
+  "url": {
+    "description": "page URL optional field specify this field if you want to get the resources for a specific page note that to obtain resource’s meta from a particular URL, you should specify the URL in this field; if you do not indicate a url when setting a task, resource’s meta in the results will be returned based on the data from the page where our crawler first saw the resource",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / items / required
      Added value: +[
+  "id"
+]
    • 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: +[
+  {
+    "filters": [
+      [
+        "resource_type",
+        "=",
+        "image"
+      ],
+      "and",
+      [
+        "size",
+        ">",
+        100000
+      ]
+    ],
+    "id": "07281559-0695-0216-0000-c269be8b7592",
+    "limit": 10,
+    "order_by": [
+      "size,desc"
+    ]
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "filters": [
+          [
+            "resource_type",
+            "=",
+            "image"
+          ],
+          "and",
+          [
+            "size",
+            ">",
+            100000
+          ]
+        ],
+        "id": "07281559-0695-0216-0000-c269be8b7592",
+        "limit": 10,
+        "order_by": [
+          "size,desc"
+        ]
+      }
+    ],
+    "properties": {
+      "filters": {
+        "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"resource_type\",\"=\",\"stylesheet\"]</code><p><code>[[\"resource_type\",\"=\",\"image\"],<br>\"and\",[\"checks.is_https\",\"=\",false]]</code><p><code>[[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\"&gt;\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">by this link.</a>",
+        "items": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "<em>ID of the task</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\">Task POST</a> endpoint<br>example:<br>\"07131248-1535-0216-1000-17384017ad04\"",
+        "type": "string"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned resources</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "offset": {
+        "description": "<em>offset in the results array of returned resources</em><br>optional field<br>default value: <code>0</code><br>maximum value: <code>2000000</code><br>if you specify the <code>10</code> value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "order_by": {
+        "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"size,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"size,desc\",\"fetch_timing.fetch_end,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "relevant_pages_filters": {
+        "description": "<em>filter the resources by relevant pages</em><br>optional field<br>you can use this field to obtain resources from pages matching to the defined parameters<br>you can apply the same filters here as available for the <a href=\"/v3/on_page/pages/\" rel=\"noopener noreferrer\" target=\"_blank\">pages endpoint</a><br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>&lt;</code>, <code>&lt;=</code>, <code>&gt;</code>, <code>&gt;=</code>, <code>=</code>, <code>&lt;&gt;</code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"checks.no_image_title\",\"=\",true]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "search_after_token": {
+        "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request",
+        "type": [
+          "string",
+          "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"
+        ]
+      },
+      "url": {
+        "description": "<em>page URL</em><br>optional field<br>specify this field if you want to get the resources for a specific page<br>note that to obtain resource's <code>meta</code> from a particular URL, you should specify the URL in this field;<br>if you do not indicate a <code>url</code> when setting a task, resource's <code>meta</code> in the results will be returned based on the data from the page where our crawler first saw the resource",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / properties
      Removed value: -{
-  "filters": {
-    "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, , , >, >=, =, , in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: [\"resource_type\",\"=\",\"stylesheet\"] [[\"resource_type\",\"=\",\"image\"], \"and\",[\"checks.is_https\",\"=\",false]] [[\"fetch_timing.duration_time\",\">\",1],\"and\",[[\"total_transfer_size\",\">\",100],\"or\",[\"checks.high_loading_time\",\"=\",true]]] The full list of possible filters is available by this link.",
-    "items": {},
-    "type": "array"
-  },
-  "id": {
-    "description": "ID of the task required field you can get this ID in the response of the Task POST endpoint example: “07131248-1535-0216-1000-17384017ad04”",
-    "type": "string"
-  },
-  "limit": {
-    "description": "the maximum number of returned resources optional field default value: 100 maximum value: 1000",
-    "type": "integer"
-  },
-  "offset": {
-    "description": "offset in the results array of returned resources optional field default value: 0 maximum value: 2000000 if you specify the 10 value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources",
-    "type": "integer"
-  },
-  "order_by": {
-    "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"size,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"size,desc\",\"fetch_timing.fetch_end,desc\"]",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "relevant_pages_filters": {
-    "description": "filter the resources by relevant pages optional field you can use this field to obtain resources from pages matching to the defined parameters you can apply the same filters here as available for the pages endpoint you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, , , >, >=, =, , in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: [\"checks.no_image_title\",\"=\",true]",
-    "items": {},
-    "type": "array"
-  },
-  "search_after_token": {
-    "description": "token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 20,000 results in a single request; by specifying the unique search_after_token value from the response array, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task ; Note: if the search_after_token is specified in the request, all other parameters should be identical to the previous request",
-    "type": "string"
-  },
-  "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"
-  },
-  "url": {
-    "description": "page URL optional field specify this field if you want to get the resources for a specific page note that to obtain resource’s meta from a particular URL, you should specify the URL in this field; if you do not indicate a url when setting a task, resource’s meta in the results will be returned based on the data from the page where our crawler first saw the resource",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "id"
-]
    • 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. Changed1 schema field changed
    • changedInput schema / properties / body / items / properties / offset / description
      Previous value: -"offset in the results array of returned resources optional field default value: 0 if you specify the 10 value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources"New value: +"offset in the results array of returned resources optional field default value: 0 maximum value: 2000000 if you specify the 10 value, the first ten resources in the results array will be omitted and the data will be provided for the successive resources"
  7. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description adds one genuinely useful non-annotation fact: usage-based billing with a $0.012 estimate and the caveat that final pricing may differ. It says nothing about rate limits, task prerequisites, or the practical tension between its 'provide you with a list' phrasing and the destructiveHint=true annotation.

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?

Two front-loaded sentences state the capability first, and the billing block is clearly delimited and short. Nothing is redundant, though the sentence about 'detailed overview of every resource' largely restates the first.

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 explanation is not required. However, for a tool whose only input is a body array keyed on a task ID from another endpoint, the description omits what an agent most needs: that a task must already exist and that this is the resource-audit step of the OnPage workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description offers zero parameter guidance (no mention of id, url, limit, offset, filters, order_by, or search_after_token). Top-level schema description coverage is reported at 0%, and the outer 'body' wrapper carries no description at all, so the agent must rely entirely on deeply nested schema prose rather than on the description to compensate.

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?

States a concrete verb and resource plainly: it returns a list of page resources — images, scripts, stylesheets, broken elements. An agent can distinguish it from siblings like links or content_parsing on the resource types named. It does not, however, explicitly separate itself from the close sibling post_dataforseo_on_page_uncrawlable_resources, which also concerns resources.

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?

There is no statement of when to use this over the many sibling on_page POST endpoints, and no prerequisites are given. Critically, nothing in the description tells the agent that this endpoint consumes an existing task ID produced by the Task POST (submit) endpoint, even though that is the required input.

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

All AIsa On-Page Audit toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources