AIsa On-Page Audit

OnPage API Force Stop

post_dataforseo_on_page_force_stop

Destructive

‌‌ This endpoint is designed to force stop the crawl process of websites you specified in a task. The execution of all the tasks associated with the IDs indicated in your request to this endpoint will be stopped. You will still be able to obtain the data on pages that have been scanned until the crawling process was stopped.

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

Input Schema

Name	Required	Description	Default
`body`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / body / items / oneOf

Previous value: -[
-  {
-    "example": [
-      {
-        "id": "08121600-1535-0216-0000-37b4c7a34453"
-      },
-      {
-        "id": "08121600-1535-0216-0000-d6a5000b6897"
-      }
-    ],
-    "properties": {
-      "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\"<p><strong>note</strong>: you can set up to 1000 <code>id</code> values as separate objects in the POST array",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "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\"<p><strong>note</strong>: you can set up to 1000 <code>id</code> values as separate objects in the POST array",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

Changed2 schema fields changedOct 16, 2026

removedInput schema / properties / body / items / anyOf

Removed value: -[
-  {
-    "example": [
-      {
-        "id": "08121600-1535-0216-0000-37b4c7a34453"
-      },
-      {
-        "id": "08121600-1535-0216-0000-d6a5000b6897"
-      }
-    ],
-    "properties": {
-      "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\"<p><strong>note</strong>: you can set up to 1000 <code>id</code> values as separate objects in the POST array",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]

addedInput schema / properties / body / items / oneOf

Added value: +[
+  {
+    "example": [
+      {
+        "id": "08121600-1535-0216-0000-37b4c7a34453"
+      },
+      {
+        "id": "08121600-1535-0216-0000-d6a5000b6897"
+      }
+    ],
+    "properties": {
+      "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\"<p><strong>note</strong>: you can set up to 1000 <code>id</code> values as separate objects in the POST array",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

Changed7 schema fields changedOct 15, 2026

addedInput schema / properties / body / example

Added value: +[
+  {
+    "id": "08121600-1535-0216-0000-37b4c7a34453"
+  },
+  {
+    "id": "08121600-1535-0216-0000-d6a5000b6897"
+  }
+]

addedInput schema / properties / body / items / anyOf

Added value: +[
+  {
+    "example": [
+      {
+        "id": "08121600-1535-0216-0000-37b4c7a34453"
+      },
+      {
+        "id": "08121600-1535-0216-0000-d6a5000b6897"
+      }
+    ],
+    "properties": {
+      "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\"<p><strong>note</strong>: you can set up to 1000 <code>id</code> values as separate objects in the POST array",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

removedInput schema / properties / body / items / properties

Removed value: -{
-  "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” note: you can set up to 1000 id values as separate objects in the POST array",
-    "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
```

Changed7 schema fields changedOct 15, 2026

removedInput schema / properties / body / example

Removed value: -[
-  {
-    "id": "08121600-1535-0216-0000-37b4c7a34453"
-  },
-  {
-    "id": "08121600-1535-0216-0000-d6a5000b6897"
-  }
-]

removedInput schema / properties / body / items / anyOf

Removed value: -[
-  {
-    "example": [
-      {
-        "id": "08121600-1535-0216-0000-37b4c7a34453"
-      },
-      {
-        "id": "08121600-1535-0216-0000-d6a5000b6897"
-      }
-    ],
-    "properties": {
-      "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\"<p><strong>note</strong>: you can set up to 1000 <code>id</code> values as separate objects in the POST array",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]

addedInput schema / properties / body / items / properties

Added value: +{
+  "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” note: you can set up to 1000 id values as separate objects in the POST array",
+    "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
```

Changed7 schema fields changedOct 15, 2026

addedInput schema / properties / body / example

Added value: +[
+  {
+    "id": "08121600-1535-0216-0000-37b4c7a34453"
+  },
+  {
+    "id": "08121600-1535-0216-0000-d6a5000b6897"
+  }
+]

addedInput schema / properties / body / items / anyOf

Added value: +[
+  {
+    "example": [
+      {
+        "id": "08121600-1535-0216-0000-37b4c7a34453"
+      },
+      {
+        "id": "08121600-1535-0216-0000-d6a5000b6897"
+      }
+    ],
+    "properties": {
+      "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\"<p><strong>note</strong>: you can set up to 1000 <code>id</code> values as separate objects in the POST array",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

removedInput schema / properties / body / items / properties

Removed value: -{
-  "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” note: you can set up to 1000 id values as separate objects in the POST array",
-    "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
```

First observedSep 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real behavioral value beyond them: it discloses that ALL tasks matching the given IDs are stopped and that already-scanned page data remains retrievable. That 'what survives the destructive action' detail is exactly the context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with purpose followed by the consequence. The embedded pricing marker is injected boilerplate rather than authorial padding, so the prose itself is efficient.

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

Completeness4/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 need no explanation, and the annotations cover the safety profile. The description supplies the operational effect and partial-data survival, leaving only parameter detail thin for a single-parameter tool.

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?

With schema description coverage reported at 0%, the description must carry parameter meaning, yet it only alludes to 'the IDs indicated in your request' without stating the id format, the source of the IDs, or the 1000-item array limit. It adds essentially nothing beyond the single bare parameter name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'force stop the crawl process of websites you specified in a task.' This clearly distinguishes it from the sibling crawl-initiation tools (post_dataforseo_on_page_submit) and the retrieval tools, so an agent can tell it apart without opening a schema.

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

Usage Guidelines3/5

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

It implies the use case (halting an in-flight crawl) and states the scope of effect, but never says when to prefer this over simply waiting or re-submitting, nor names any alternative. Usage is inferable rather than prescribed.

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 tools Inspect

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

Need Help?