Skip to main content
Glama

AIsa On-Page Audit

OnPage API Raw HTML

post_dataforseo_on_page_raw_html
Destructive

‌‌ This endpoint returns the HTML of a page you indicate in the request.

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. Changed1 schema field changed
    • changedInput schema / properties / body / items / oneOf
      Previous value: -[
      -  {
      -    "example": [
      -      {
      -        "id": "07281559-0695-0216-0000-c269be8b7592",
      -        "url": "https://dataforseo.com/apis"
      -      }
      -    ],
      -    "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\"",
      -        "type": "string"
      -      },
      -      "url": {
      -        "description": "<em>page url</em><br><strong>required field</strong><br>the absolute URL of a page to request HTML<br><strong>Note:</strong> this field is optional if the task was set using the <a href=\"/v3/on_page/instant_pages/\">Instant Pages endpoint</a>",
      -        "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\"",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "<em>page url</em><br><strong>required field</strong><br>the absolute URL of a page to request HTML<br><strong>Note:</strong> this field is optional if the task was set using the <a href=\"/v3/on_page/instant_pages/\">Instant Pages endpoint</a>",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  2. Changed2 schema fields changed
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
      -  {
      -    "example": [
      -      {
      -        "id": "07281559-0695-0216-0000-c269be8b7592",
      -        "url": "https://dataforseo.com/apis"
      -      }
      -    ],
      -    "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\"",
      -        "type": "string"
      -      },
      -      "url": {
      -        "description": "<em>page url</em><br><strong>required field</strong><br>the absolute URL of a page to request HTML<br><strong>Note:</strong> this field is optional if the task was set using the <a href=\"/v3/on_page/instant_pages/\">Instant Pages endpoint</a>",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / body / items / oneOf
      Added value: +[
      +  {
      +    "example": [
      +      {
      +        "id": "07281559-0695-0216-0000-c269be8b7592",
      +        "url": "https://dataforseo.com/apis"
      +      }
      +    ],
      +    "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\"",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "<em>page url</em><br><strong>required field</strong><br>the absolute URL of a page to request HTML<br><strong>Note:</strong> this field is optional if the task was set using the <a href=\"/v3/on_page/instant_pages/\">Instant Pages endpoint</a>",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  3. Changed7 schema fields changed
    • addedInput schema / properties / body / example
      Added value: +[
      +  {
      +    "id": "07281559-0695-0216-0000-c269be8b7592",
      +    "url": "https://dataforseo.com/apis"
      +  }
      +]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
      +  {
      +    "example": [
      +      {
      +        "id": "07281559-0695-0216-0000-c269be8b7592",
      +        "url": "https://dataforseo.com/apis"
      +      }
      +    ],
      +    "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\"",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "<em>page url</em><br><strong>required field</strong><br>the absolute URL of a page to request HTML<br><strong>Note:</strong> this field is optional if the task was set using the <a href=\"/v3/on_page/instant_pages/\">Instant Pages endpoint</a>",
      +        "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”",
      -    "type": "string"
      -  },
      -  "url": {
      -    "description": "page url required field the absolute URL of a page to request HTML Note: this field is optional if the task was set using the Instant Pages endpoint",
      -    "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: -[
      -  {
      -    "id": "07281559-0695-0216-0000-c269be8b7592",
      -    "url": "https://dataforseo.com/apis"
      -  }
      -]
    • removedInput schema / properties / body / items / anyOf
      Removed value: -[
      -  {
      -    "example": [
      -      {
      -        "id": "07281559-0695-0216-0000-c269be8b7592",
      -        "url": "https://dataforseo.com/apis"
      -      }
      -    ],
      -    "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\"",
      -        "type": "string"
      -      },
      -      "url": {
      -        "description": "<em>page url</em><br><strong>required field</strong><br>the absolute URL of a page to request HTML<br><strong>Note:</strong> this field is optional if the task was set using the <a href=\"/v3/on_page/instant_pages/\">Instant Pages endpoint</a>",
      -        "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”",
      +    "type": "string"
      +  },
      +  "url": {
      +    "description": "page url required field the absolute URL of a page to request HTML Note: this field is optional if the task was set using the Instant Pages endpoint",
      +    "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: +[
      +  {
      +    "id": "07281559-0695-0216-0000-c269be8b7592",
      +    "url": "https://dataforseo.com/apis"
      +  }
      +]
    • addedInput schema / properties / body / items / anyOf
      Added value: +[
      +  {
      +    "example": [
      +      {
      +        "id": "07281559-0695-0216-0000-c269be8b7592",
      +        "url": "https://dataforseo.com/apis"
      +      }
      +    ],
      +    "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\"",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "<em>page url</em><br><strong>required field</strong><br>the absolute URL of a page to request HTML<br><strong>Note:</strong> this field is optional if the task was set using the <a href=\"/v3/on_page/instant_pages/\">Instant Pages endpoint</a>",
      +        "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”",
      -    "type": "string"
      -  },
      -  "url": {
      -    "description": "page url required field the absolute URL of a page to request HTML Note: this field is optional if the task was set using the Instant Pages endpoint",
      -    "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. First observed

TDQS

C2.8/5.0
Behavior1/5

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

The description describes a retrieval ('returns the HTML of a page') while the annotations declare readOnlyHint=false and destructiveHint=true, so the safety profile an agent receives is internally inconsistent. The only added behavioral context is the billing estimate (~$0.012), which does not resolve the destructive/read conflict.

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?

The visible text is tight, one purpose sentence plus a short pricing note, and the purpose is front-loaded. It is marred only by leading zero-width characters and the injected boilerplate pricing comment block, which are formatting noise rather than padding.

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 values need not be explained. However, for a task-scoped endpoint the description should have flagged the dependency on a previously created task and the billed, non-idempotent nature of the call, which it leaves to the schema or nowhere at all.

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

Parameters3/5

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

The description adds nothing about the single body parameter (task id / page url). The nested schema text does fully document both required fields, including that url is optional when Instant Pages was used, so the schema carries the semantics; a 3 baseline is appropriate despite the reported 0% top-level coverage.

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 concrete verb and resource: it 'returns the HTML of a page you indicate in the request,' matching the tool name (raw_html). That is enough for an agent to know what it does, but it never distinguishes this endpoint from the many adjacent OnPage endpoints (content_parsing, microdata, resources), 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?

There is no when-to-use guidance, no when-not-to-use, and no mention of alternative siblings such as post_dataforseo_on_page_content_parsing. The description also omits the critical prerequisite that a task must already exist (via Task POST) before this call is meaningful, even though the schema hints at it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources