Skip to main content
Glama

Honeyfield Marketing MCP

DataForSEO: On-page crawl results

dfs_onpage_crawl_results
Read-only

Ergebnisse eines mit dfs_onpage_crawl gestarteten Crawls. section: 'summary' | 'pages' | 'links' | 'redirect_chains' | 'non_indexable' | 'duplicate_content' | 'duplicate_tags' | 'microdata'. 'duplicate_content'/'microdata' brauchen zusaetzlich url (Seite aus 'pages'), 'duplicate_tags' braucht tag_type ('duplicate_title'|'duplicate_description'). Solange der Crawl laeuft: Fortschritt statt Ergebnis. task_id genau wie von dfs_onpage_crawl geliefert (Buchstaben, Ziffern, _ und -), sonst Fehler invalid_task_id. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "task_id": "<task_id>"
    },
    "name": "dfs_onpage_crawl_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
limitNo
sectionNosummary
task_idYes
tag_typeNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond that — while the crawl is still running you get progress instead of results, and a malformed task_id yields an explicit invalid_task_id error. Pagination via `limit` is not described, which keeps it below 5.

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?

Dense and front-loaded — purpose first, then section routing, then runtime behavior, then task_id/workspace notes. It is a semicolon-chained run-on that takes a second read, but essentially no sentence is wasted.

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 available, return values need no explanation, and the description covers the preconditions, section semantics, and error mode an agent needs. The one remaining gap is what `limit` controls and whether results are paginated.

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

Parameters4/5

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

Schema description coverage is 0% and section has no enum in the schema, so the description carries the load and does it well: it enumerates all eight section values, states the conditional url/tag_type requirements, and pins the task_id character set. Only `limit` is left undocumented, so it is strong but not exhaustive.

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?

States a specific verb+resource: it returns the results of a crawl previously started with dfs_onpage_crawl, which immediately distinguishes it from dfs_onpage_crawl (starts a crawl) and dfs_onpage_instant (single-page, no task). The set of retrievable sections is named up front, so the agent knows the shape of what it can get back.

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

Usage Guidelines4/5

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

Clearly tells the agent it must first run dfs_onpage_crawl and pass the resulting task_id, and gives conditional routing between sections ('duplicate_content'/'microdata' need `url`, 'duplicate_tags' needs `tag_type`). It does not explicitly contrast with dfs_onpage_instant or say when a section is the wrong choice for a given question, so it falls short of a full 5.

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