Rowfeed Search & Market Data

rowfeed/da-pa-checker

rowfeed--da-pa-checker

Destructive

This tool calls the Actor "rowfeed/da-pa-checker" and retrieves its output results. Actor description: Check domain authority (DA), page authority (PA) and spam score for up to 10,000 domains or URLs at once, plus referring domains. A bulk Moz-style DA checker and website authority checker on licensed backlink data.

Input Schema

Name	Required	Description	Default
`targets`	No	Domains get domain authority, spam score and referring domains. Page URLs also get page authority (PA). Up to 10,000. Example values: ["apify.com","https://apify.com/store","bbc.co.uk"]
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.

Output Schema

Name	Required	Description
`tip`	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
`runId`	Yes	Actor run ID
`stats`	No	Run statistics
`status`	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
`actorId`	Yes	Stable Apify Actor ID from the run record
`summary`	Yes	Past-tense summary of the run state
`exitCode`	No	Actor process exit code; populated for terminal states (especially FAILED)
`nextStep`	Yes	One primary follow-up action with identifiers interpolated
`storages`	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
`actorName`	No	"username/actor-name"
`startedAt`	No	ISO timestamp when the run started
`finishedAt`	No	ISO timestamp when the run finished (terminal states only)
`statusMessage`	No	Pass-through from Apify run.statusMessage
`apifyConsoleUrl`	No	Personalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "checked_at": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "domain_authority": {
+      "type": "number"
+    },
+    "domain_rank": {
+      "type": "number"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "page": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "page_authority": {
+      "type": [
+        "null",
+        "number"
+      ]
+    },
+    "page_rank": {
+      "type": [
+        "null",
+        "number"
+      ]
+    },
+    "referring_domains": {
+      "type": "number"
+    },
+    "referring_domains_nofollow": {
+      "type": "number"
+    },
+    "referring_main_domains": {
+      "type": "number"
+    },
+    "spam_score": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 6, 2026
- addedInput schema / properties / targets / prefill
```
Added value: +[
+  "apify.com",
+  "https://apify.com/store",
+  "bbc.co.uk"
+]
```

Changed1 schema field changedNov 6, 2026

addedInput schema / description

Added value: +"Live lookups need a paid Apify plan (any plan). The pre-filled example works on the free plan."

Changed1 schema field changedNov 5, 2026

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "checked_at": {
-      "type": "string"
-    },
-    "domain": {
-      "type": "string"
-    },
-    "domain_authority": {
-      "type": "number"
-    },
-    "domain_rank": {
-      "type": "number"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "page": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "page_authority": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "page_rank": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "referring_domains": {
-      "type": "number"
-    },
-    "referring_domains_nofollow": {
-      "type": "number"
-    },
-    "referring_main_domains": {
-      "type": "number"
-    },
-    "spam_score": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedNov 5, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "checked_at": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "domain_authority": {
+      "type": "number"
+    },
+    "domain_rank": {
+      "type": "number"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "page": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "page_authority": {
+      "type": [
+        "null",
+        "number"
+      ]
+    },
+    "page_rank": {
+      "type": [
+        "null",
+        "number"
+      ]
+    },
+    "referring_domains": {
+      "type": "number"
+    },
+    "referring_domains_nofollow": {
+      "type": "number"
+    },
+    "referring_main_domains": {
+      "type": "number"
+    },
+    "spam_score": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 4, 2026

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "checked_at": {
-      "type": "string"
-    },
-    "domain": {
-      "type": "string"
-    },
-    "domain_authority": {
-      "type": "number"
-    },
-    "domain_rank": {
-      "type": "number"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "note": {
-      "type": "string"
-    },
-    "page": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "page_authority": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "page_rank": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "referring_domains": {
-      "type": "number"
-    },
-    "referring_domains_nofollow": {
-      "type": "number"
-    },
-    "referring_main_domains": {
-      "type": "number"
-    },
-    "spam_score": {
-      "type": [
-        "number",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

Changed2 schema fields changedNov 4, 2026
- addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / note
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / spam_score / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedNov 2, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "checked_at": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "domain_authority": {
+      "type": "number"
+    },
+    "domain_rank": {
+      "type": "number"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "page": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "page_authority": {
+      "type": [
+        "null",
+        "number"
+      ]
+    },
+    "page_rank": {
+      "type": [
+        "null",
+        "number"
+      ]
+    },
+    "referring_domains": {
+      "type": "number"
+    },
+    "referring_domains_nofollow": {
+      "type": "number"
+    },
+    "referring_main_domains": {
+      "type": "number"
+    },
+    "spam_score": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 1, 2026

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "checked_at": {
-      "type": "string"
-    },
-    "domain": {
-      "type": "string"
-    },
-    "domain_authority": {
-      "type": "number"
-    },
-    "domain_rank": {
-      "type": "number"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "page": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "page_authority": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "page_rank": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "referring_domains": {
-      "type": "number"
-    },
-    "referring_domains_nofollow": {
-      "type": "number"
-    },
-    "referring_main_domains": {
-      "type": "number"
-    },
-    "spam_score": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

AddedOct 30, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The first sentence discloses the important operational fact that this invokes an Actor run and returns its output rather than doing a direct lookup — useful context beyond the annotations. Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, and the description does not contradict them. However, the wait-for-terminal-state behavior, the possibility of a capped response with a pending run, and the paid-plan requirement all live in the schema text rather than in the description.

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?

Two sentences, no padding beyond the boilerplate 'This tool calls the Actor ... and retrieves its output results' wrapper that generic MCP-Actor tools carry. The substantive content is compact, but the leading sentence conveys little that the tool name and annotations do not already signal.

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?

Because an output schema exists, the description need not explain return values, and the input schema carries the billing prerequisite and wait semantics. What remains missing is the differentiating context an agent needs when choosing among several SEO lookup siblings, which the description does not supply.

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%, so both parameters (targets and waitSecs) are fully documented in structured fields, including the DA vs. PA distinction and the 0–45 second cap. The description adds only the 'up to 10,000' scale figure, which the schema already states, 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?

The description gives a specific verb and resource: check domain authority, page authority, and spam score for up to 10,000 domains or URLs, plus referring domains. The 'Moz-style bulk DA checker' framing makes the output metric clear. It never names the closest sibling (rowfeed--backlink-checker), so the distinction from that tool is left for the agent to infer.

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 only implied by the metric names: an agent can deduce that this is for bulk authority scoring rather than for link enumeration. There is no explicit when-to-use or when-not-to-use statement, and no alternatives are named, despite rowfeed--backlink-checker, rowfeed--seo-site-audit, and rowfeed--website-traffic-checker sharing the same neighborhood.

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

All Rowfeed Search & Market Data 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.

rowfeed/da-pa-checker

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources