Skip to main content
Glama

AIsa On-Page Audit

by one.aisa
OverviewDiscussionsAdmin

Keyword Density

post_dataforseo_on_page_keyword_density
Destructive

‌‌ This endpoint will provide you with keyword density and keyword frequency data for terms appearing on the specified website or web page. You can filter and sort the data that will be retrieved with this API call.

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>=</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>[\"keyword\",\"=\",\"%seo%\"]</code><p><code>[[\"keyword\",\"=\",\"%seo%\"],<br>\"and\",<br>[\"frequency\",\"&lt;\",\"6\"]]</code><p><code>[[\"keyword\",\"not_like\",\"%seo%\"],<br>\"and\",<br>[[\"frequency\",\"&gt;\",\"6\"],\"or\",[\"density\",\"&gt;\",\"0.02\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" target=\"_blank\" rel=\"noopener noreferrer\">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"
+      },
+      "keyword_length": {
+        "description": "<em>number of words for a keyword</em><br><strong>required field</strong><br>possible values:<br><code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>",
+        "type": "integer"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned keywords</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "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>[\"frequency,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>[\"keyword,asc\",\"frequency,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "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><strong>if you do not specify a page here, the results will be provided for the whole website</strong><br>if you use this field, the API response will contain only keywords from the specified page<br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / items / oneOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "filters": [
-          "frequency",
-          ">",
-          5
-        ],
-        "id": "09101923-1535-0216-0000-2389a8854b70",
-        "keyword_length": 2,
-        "url": "https://dataforseo.com/"
-      }
-    ],
-    "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>=</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>[\"keyword\",\"=\",\"%seo%\"]</code><p><code>[[\"keyword\",\"=\",\"%seo%\"],<br>\"and\",<br>[\"frequency\",\"&lt;\",\"6\"]]</code><p><code>[[\"keyword\",\"not_like\",\"%seo%\"],<br>\"and\",<br>[[\"frequency\",\"&gt;\",\"6\"],\"or\",[\"density\",\"&gt;\",\"0.02\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" target=\"_blank\" rel=\"noopener noreferrer\">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"
-      },
-      "keyword_length": {
-        "description": "<em>number of words for a keyword</em><br><strong>required field</strong><br>possible values:<br><code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>",
-        "type": "integer"
-      },
-      "limit": {
-        "description": "<em>the maximum number of returned keywords</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
-        "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>[\"frequency,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>[\"keyword,asc\",\"frequency,desc\"]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "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><strong>if you do not specify a page here, the results will be provided for the whole website</strong><br>if you use this field, the API response will contain only keywords from the specified page<br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-]
  2. Changed2 schema fields changed
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "filters": [
-          "frequency",
-          ">",
-          5
-        ],
-        "id": "09101923-1535-0216-0000-2389a8854b70",
-        "keyword_length": 2,
-        "url": "https://dataforseo.com/"
-      }
-    ],
-    "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>=</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>[\"keyword\",\"=\",\"%seo%\"]</code><p><code>[[\"keyword\",\"=\",\"%seo%\"],<br>\"and\",<br>[\"frequency\",\"&lt;\",\"6\"]]</code><p><code>[[\"keyword\",\"not_like\",\"%seo%\"],<br>\"and\",<br>[[\"frequency\",\"&gt;\",\"6\"],\"or\",[\"density\",\"&gt;\",\"0.02\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" target=\"_blank\" rel=\"noopener noreferrer\">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"
-      },
-      "keyword_length": {
-        "description": "<em>number of words for a keyword</em><br><strong>required field</strong><br>possible values:<br><code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>",
-        "type": "integer"
-      },
-      "limit": {
-        "description": "<em>the maximum number of returned keywords</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
-        "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>[\"frequency,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>[\"keyword,asc\",\"frequency,desc\"]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "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><strong>if you do not specify a page here, the results will be provided for the whole website</strong><br>if you use this field, the API response will contain only keywords from the specified page<br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / body / items / oneOf
      Added value: +[
+  {
+    "example": [
+      {
+        "filters": [
+          "frequency",
+          ">",
+          5
+        ],
+        "id": "09101923-1535-0216-0000-2389a8854b70",
+        "keyword_length": 2,
+        "url": "https://dataforseo.com/"
+      }
+    ],
+    "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>=</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>[\"keyword\",\"=\",\"%seo%\"]</code><p><code>[[\"keyword\",\"=\",\"%seo%\"],<br>\"and\",<br>[\"frequency\",\"&lt;\",\"6\"]]</code><p><code>[[\"keyword\",\"not_like\",\"%seo%\"],<br>\"and\",<br>[[\"frequency\",\"&gt;\",\"6\"],\"or\",[\"density\",\"&gt;\",\"0.02\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" target=\"_blank\" rel=\"noopener noreferrer\">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"
+      },
+      "keyword_length": {
+        "description": "<em>number of words for a keyword</em><br><strong>required field</strong><br>possible values:<br><code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>",
+        "type": "integer"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned keywords</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "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>[\"frequency,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>[\"keyword,asc\",\"frequency,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "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><strong>if you do not specify a page here, the results will be provided for the whole website</strong><br>if you use this field, the API response will contain only keywords from the specified page<br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+]
  3. Changed7 schema fields changed
    • addedInput schema / properties / body / example
      Added value: +[
+  {
+    "filters": [
+      "frequency",
+      ">",
+      5
+    ],
+    "id": "09101923-1535-0216-0000-2389a8854b70",
+    "keyword_length": 2,
+    "url": "https://dataforseo.com/"
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "filters": [
+          "frequency",
+          ">",
+          5
+        ],
+        "id": "09101923-1535-0216-0000-2389a8854b70",
+        "keyword_length": 2,
+        "url": "https://dataforseo.com/"
+      }
+    ],
+    "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>=</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>[\"keyword\",\"=\",\"%seo%\"]</code><p><code>[[\"keyword\",\"=\",\"%seo%\"],<br>\"and\",<br>[\"frequency\",\"&lt;\",\"6\"]]</code><p><code>[[\"keyword\",\"not_like\",\"%seo%\"],<br>\"and\",<br>[[\"frequency\",\"&gt;\",\"6\"],\"or\",[\"density\",\"&gt;\",\"0.02\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" target=\"_blank\" rel=\"noopener noreferrer\">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"
+      },
+      "keyword_length": {
+        "description": "<em>number of words for a keyword</em><br><strong>required field</strong><br>possible values:<br><code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>",
+        "type": "integer"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned keywords</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "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>[\"frequency,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>[\"keyword,asc\",\"frequency,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "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><strong>if you do not specify a page here, the results will be provided for the whole website</strong><br>if you use this field, the API response will contain only keywords from the specified page<br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)",
+        "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: [\"keyword\",\"=\",\"%seo%\"] [[\"keyword\",\"=\",\"%seo%\"], \"and\", [\"frequency\",\"<\",\"6\"]] [[\"keyword\",\"not_like\",\"%seo%\"], \"and\", [[\"frequency\",\">\",\"6\"],\"or\",[\"density\",\">\",\"0.02\"]]] 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"
-  },
-  "keyword_length": {
-    "description": "number of words for a keyword required field possible values: 1, 2, 3, 4, 5",
-    "type": "integer"
-  },
-  "limit": {
-    "description": "the maximum number of returned keywords optional field default value: 100 maximum value: 1000",
-    "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: [\"frequency,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: [\"keyword,asc\",\"frequency,desc\"]",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "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 if you do not specify a page here, the results will be provided for the whole website if you use this field, the API response will contain only keywords from the specified page a page should be specified with absolute URL (including http:// or https://)",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "id",
-  "keyword_length"
-]
    • 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": [
-      "frequency",
-      ">",
-      5
-    ],
-    "id": "09101923-1535-0216-0000-2389a8854b70",
-    "keyword_length": 2,
-    "url": "https://dataforseo.com/"
-  }
-]
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
-  {
-    "example": [
-      {
-        "filters": [
-          "frequency",
-          ">",
-          5
-        ],
-        "id": "09101923-1535-0216-0000-2389a8854b70",
-        "keyword_length": 2,
-        "url": "https://dataforseo.com/"
-      }
-    ],
-    "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>=</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>[\"keyword\",\"=\",\"%seo%\"]</code><p><code>[[\"keyword\",\"=\",\"%seo%\"],<br>\"and\",<br>[\"frequency\",\"&lt;\",\"6\"]]</code><p><code>[[\"keyword\",\"not_like\",\"%seo%\"],<br>\"and\",<br>[[\"frequency\",\"&gt;\",\"6\"],\"or\",[\"density\",\"&gt;\",\"0.02\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" target=\"_blank\" rel=\"noopener noreferrer\">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"
-      },
-      "keyword_length": {
-        "description": "<em>number of words for a keyword</em><br><strong>required field</strong><br>possible values:<br><code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>",
-        "type": "integer"
-      },
-      "limit": {
-        "description": "<em>the maximum number of returned keywords</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
-        "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>[\"frequency,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>[\"keyword,asc\",\"frequency,desc\"]</code>",
-        "items": {
-          "type": "string"
-        },
-        "type": [
-          "array",
-          "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><strong>if you do not specify a page here, the results will be provided for the whole website</strong><br>if you use this field, the API response will contain only keywords from the specified page<br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)",
-        "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: [\"keyword\",\"=\",\"%seo%\"] [[\"keyword\",\"=\",\"%seo%\"], \"and\", [\"frequency\",\"<\",\"6\"]] [[\"keyword\",\"not_like\",\"%seo%\"], \"and\", [[\"frequency\",\">\",\"6\"],\"or\",[\"density\",\">\",\"0.02\"]]] 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"
+  },
+  "keyword_length": {
+    "description": "number of words for a keyword required field possible values: 1, 2, 3, 4, 5",
+    "type": "integer"
+  },
+  "limit": {
+    "description": "the maximum number of returned keywords optional field default value: 100 maximum value: 1000",
+    "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: [\"frequency,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: [\"keyword,asc\",\"frequency,desc\"]",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "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 if you do not specify a page here, the results will be provided for the whole website if you use this field, the API response will contain only keywords from the specified page a page should be specified with absolute URL (including http:// or https://)",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / items / required
      Added value: +[
+  "id",
+  "keyword_length"
+]
    • 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": [
+      "frequency",
+      ">",
+      5
+    ],
+    "id": "09101923-1535-0216-0000-2389a8854b70",
+    "keyword_length": 2,
+    "url": "https://dataforseo.com/"
+  }
+]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
+  {
+    "example": [
+      {
+        "filters": [
+          "frequency",
+          ">",
+          5
+        ],
+        "id": "09101923-1535-0216-0000-2389a8854b70",
+        "keyword_length": 2,
+        "url": "https://dataforseo.com/"
+      }
+    ],
+    "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>=</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>[\"keyword\",\"=\",\"%seo%\"]</code><p><code>[[\"keyword\",\"=\",\"%seo%\"],<br>\"and\",<br>[\"frequency\",\"&lt;\",\"6\"]]</code><p><code>[[\"keyword\",\"not_like\",\"%seo%\"],<br>\"and\",<br>[[\"frequency\",\"&gt;\",\"6\"],\"or\",[\"density\",\"&gt;\",\"0.02\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/on_page/filters_and_thresholds/?bash\" target=\"_blank\" rel=\"noopener noreferrer\">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"
+      },
+      "keyword_length": {
+        "description": "<em>number of words for a keyword</em><br><strong>required field</strong><br>possible values:<br><code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>",
+        "type": "integer"
+      },
+      "limit": {
+        "description": "<em>the maximum number of returned keywords</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>",
+        "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>[\"frequency,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>[\"keyword,asc\",\"frequency,desc\"]</code>",
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "array",
+          "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><strong>if you do not specify a page here, the results will be provided for the whole website</strong><br>if you use this field, the API response will contain only keywords from the specified page<br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)",
+        "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: [\"keyword\",\"=\",\"%seo%\"] [[\"keyword\",\"=\",\"%seo%\"], \"and\", [\"frequency\",\"<\",\"6\"]] [[\"keyword\",\"not_like\",\"%seo%\"], \"and\", [[\"frequency\",\">\",\"6\"],\"or\",[\"density\",\">\",\"0.02\"]]] 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"
-  },
-  "keyword_length": {
-    "description": "number of words for a keyword required field possible values: 1, 2, 3, 4, 5",
-    "type": "integer"
-  },
-  "limit": {
-    "description": "the maximum number of returned keywords optional field default value: 100 maximum value: 1000",
-    "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: [\"frequency,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: [\"keyword,asc\",\"frequency,desc\"]",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "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 if you do not specify a page here, the results will be provided for the whole website if you use this field, the API response will contain only keywords from the specified page a page should be specified with absolute URL (including http:// or https://)",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / items / required
      Removed value: -[
-  "id",
-  "keyword_length"
-]
    • 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 / filters / description
      Previous value: -"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: [\"keyword\",\"=\",\"%seo%\"] [[\"keyword\",\"=\",\"%seo%\"], \"and\", [\"frequency\",\" [[\"keyword\",\"not_like\",\"%seo%\"], \"and\", [[\"frequency\",\">\",\"6\"],\"or\",[\"density\",\">\",\"0.02\"]]] The full list of possible filters is available by this link."New value: +"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: [\"keyword\",\"=\",\"%seo%\"] [[\"keyword\",\"=\",\"%seo%\"], \"and\", [\"frequency\",\"<\",\"6\"]] [[\"keyword\",\"not_like\",\"%seo%\"], \"and\", [[\"frequency\",\">\",\"6\"],\"or\",[\"density\",\">\",\"0.02\"]]] The full list of possible filters is available by this link."
  7. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations carry the safety profile (openWorld, destructive, non-idempotent) and the auto-injected pricing note discloses cost, so the bar is lower. The description adds that filtering/sorting are supported, but it does not reconcile the tension between its 'provide you with data' framing and the destructive/non-idempotent hints, nor does it disclose the task-ID prerequisite the schema reveals.

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 plus the auto-injected pricing block; the core purpose leads. The trailing 'You can filter and sort the data that will be retrieved with this API call' is filler that repeats the schema, but overall it is tight and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values needn't be described, but for a nested-filter endpoint that requires a task ID from Task POST, the description omits the entire workflow prerequisite and any link to the sibling submit/task_post step. An agent could not reliably invoke this correctly from the description alone.

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 context metric reports 0% schema coverage and the top-level 'body' wrapper is indeed undocumented, but the nested item schema is actually rich (id, url, limit, filters, order_by, keyword_length all explained with examples). The description adds essentially nothing beyond 'filter and sort,' which the schema already documents far better.

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 and resource: it 'provides keyword density and keyword frequency data for terms appearing on the specified website or web page.' That is clear enough for an agent to know what comes back, though it never distinguishes itself from the many sibling on_page tools (content_parsing, summary, microdata, etc.), so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'You can filter and sort the data,' which is a capability statement, not a when-to-use rule. There is no mention of when to pick this over the sibling on_page endpoints, no exclusions, and no prerequisite that the schema implies (an 'id' obtained from the Task POST endpoint).

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