AIsa SEO & AI Visibility

OnPage API Summary

get_dataforseo_on_page_summary

Read-onlyIdempotent

‌ Using this function, you can get the overall information on a website as well as drill down into exact on-page issues of a website that has been scanned. As a result, you will know what functions to use for receiving detailed data for each of the found issues.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_dataforseo_on_page_summary"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	<em>task identifier</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href="/v3/on_page/task_post/" target="_blank" rel="noopener noreferrer">Task POST</a> endpoint<br>example:<br>“07131248-1535-0216-1000-17384017ad04”

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

changedInput schema / properties / id / description

Previous value: -"task identifier required field you can get this ID in the response of the Task POST endpoint example: “07131248-1535-0216-1000-17384017ad04”"New value: +"<em>task identifier</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\" target=\"_blank\" rel=\"noopener noreferrer\">Task POST</a> endpoint<br>example:<br>“07131248-1535-0216-1000-17384017ad04”"

addedInput schema / properties / id / example

Added value: +"00000000-0000-0000-0000-000000000000"

addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

Changed3 schema fields changedOct 15, 2026

changedInput schema / properties / id / description

Previous value: -"<em>task identifier</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\" target=\"_blank\" rel=\"noopener noreferrer\">Task POST</a> endpoint<br>example:<br>“07131248-1535-0216-1000-17384017ad04”"New value: +"task identifier required field you can get this ID in the response of the Task POST endpoint example: “07131248-1535-0216-1000-17384017ad04”"

removedInput schema / properties / id / example

Removed value: -"00000000-0000-0000-0000-000000000000"

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

Changed3 schema fields changedOct 15, 2026

changedInput schema / properties / id / description

Previous value: -"task identifier required field you can get this ID in the response of the Task POST endpoint example: “07131248-1535-0216-1000-17384017ad04”"New value: +"<em>task identifier</em><br><strong>required field</strong><br>you can get this ID in the response of the <a href=\"/v3/on_page/task_post/\" target=\"_blank\" rel=\"noopener noreferrer\">Task POST</a> endpoint<br>example:<br>“07131248-1535-0216-1000-17384017ad04”"

addedInput schema / properties / id / example

Added value: +"00000000-0000-0000-0000-000000000000"

addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / id / description

Previous value: -"DataForSEO task ID."New value: +"task identifier required field you can get this ID in the response of the Task POST endpoint example: “07131248-1535-0216-1000-17384017ad04”"

First observedSep 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuine extra context beyond the annotations: usage-based billing with a ~$0.012 default request estimate and a note that final settlement may differ — useful cost behavior an agent cannot get from structured fields.

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

Conciseness3/5

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

The core sentence is reasonably front-loaded but runs on with an awkward 'as well as drill down into exact on-page issues' clause, and it opens with a stray zero-width character artifact. The pricing block is boilerplate but useful, so it earns partial credit rather than penalty.

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?

With an output schema present, the description need not explain return values, and annotations plus a fully documented schema cover safety and input. The remaining gap is that it never states the scan must be complete/that this reads results of a POST task, which is the main thing an agent could get wrong.

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?

Schema description coverage is 100% for the single 'id' parameter, and the schema already explains how to obtain the task identifier from the Task POST response, including an example. The description adds nothing about the parameter, so the baseline 3 is appropriate.

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

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource — retrieve the overall summary of an already-scanned site's on-page data by task ID. It also positions itself against the many detailed siblings (it tells you which detailed functions to call next), though the phrasing 'get the overall information on a website' is looser than it needs to be.

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?

Usage is implied: use this to get an overview and then decide which detailed endpoints to call. It does not explicitly name the alternative detailed sibling tools or state a precondition (e.g. the scan task must have finished), so the guidance stays at the inference level.

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

All AIsa SEO & AI Visibility tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?