Urlscan Io

Domain

domain

Read-onlyIdempotent

Search urlscan.io past scan results for a specific domain (no API key required); returns scan records including URL, verdict, screenshot link, and scan date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`took`	No	Query execution time in milliseconds
`total`	No	Total number of results for this domain
`results`	No	Array of scan results for the domain
`has_more`	No	Whether more results are available

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "domain": "example.com"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results for a specific domain",
+  "properties": {
+    "has_more": {
+      "description": "Whether more results are available",
+      "type": "boolean"
+    },
+    "results": {
+      "description": "Array of scan results for the domain",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "took": {
+      "description": "Query execution time in milliseconds",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of results for this domain",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds transparency by stating no API key needed and specifying return fields (URL, verdict, screenshot link, scan date), which is useful beyond annotations.

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

Conciseness5/5

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

Single sentence, front-loaded with action and resource, no wasted words. Highly concise and structured.

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?

Given the tool's simplicity (1 parameter, output schema present), the description covers the purpose, prerequisites, and return value highlights. It is complete for an agent to use correctly.

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 0%. The description adds 'specific domain' but no format or constraints beyond the parameter name. It provides minimal added semantics.

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 description clearly states the verb 'search', the resource 'urlscan.io past scan results', and the target 'specific domain'. It distinguishes itself from sibling tools by focusing on domain-specific lookup.

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?

The description mentions 'no API key required' which is a helpful prerequisite, but it does not provide when to use this tool versus alternatives or any exclusions. It lacks explicit usage guidance.

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

All Urlscan Io 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.