TidyTools Free Web Data

referring_domains

Read-only

Looks up one domain's referring domains. Returns a limited free result and paid upgrade links. Apify Actor links can be paid with x402 via Apify, no Apify account needed. Send Authorization: Bearer tt_… for full results billed in TidyTools credits. Use for one domain. Not for batch work or unrestricted monitoring. Free: 3 per IP per UTC day; shared AI caller/ASN pool 50; 300 globally per day.

Input Schema

Name	Required	Description	Default
`url`	No	Website URL alias for domain; supply one of domain or url.
`domain`	No	One public domain.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "domain"
+    ]
+  },
+  {
+    "required": [
+      "url"
+    ]
+  }
+]

addedInput schema / properties / url

Added value: +{
+  "description": "Website URL alias for domain; supply one of domain or url.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "domain"
-]New value: +[]

AddedOct 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behavior: results are limited unless authenticated, paid upgrade links are returned, full results require a Bearer token billed in TidyTools credits, and free-tier quotas vary by IP and shared caller pool. These are meaningful operational details an agent would not get from the annotations alone.

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 description is front-loaded with purpose and return behavior, then adds auth and quota details without filler. It is somewhat dense with multiple operational facts, but each sentence contributes relevant context for calling the tool correctly.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately explains what comes back: a limited free result plus paid upgrade links. It also covers authentication, billing, free-tier quotas, and scope limitations, which is enough for an agent to invoke the tool with realistic expectations.

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 both the domain and url parameters, and the schema already explains that either one may be supplied. The description reinforces the single-domain scope but adds no parameter-specific syntax or constraints beyond what the schema provides, so baseline 3 is appropriate.

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 first sentence states a specific verb and resource: looking up one domain's referring domains. It also scopes the tool to a single domain and explicitly excludes batch work and unrestricted monitoring, so an agent can tell what this tool is for without opening the schema.

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?

The description gives clear usage context ('Use for one domain') and explicit exclusions ('Not for batch work or unrestricted monitoring'), which helps an agent avoid misuse. It does not name a specific alternative sibling tool for batch work, so it falls short of a 5.

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

All TidyTools Free Web 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.

Resources

Need Help?