Skip to main content
Glama

Urlscan Io Search

urlscan_io_search
Read-onlyIdempotent

Search the public urlscan.io archive of website scans using urlscan query syntax, for example page.domain:example.com, task.url, ip, asn, or filename terms, with size and search_after paging and no API key needed. Returns matching scan records with the scanned URL, page domain, IP, ASN, server, scan date, and the scan uuid used to pull the full report. Answers which pages urlscan has already scanned for a domain, brand, or infrastructure indicator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "phishing"
    },
    "name": "urlscan_io_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
queryYes
search_afterNo

Output Schema

NameRequiredDescriptionDefault
tookNoQuery execution time in milliseconds
totalNoTotal number of results available
resultsNoArray of scan results matching the query
has_moreNoWhether more results are available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses that no API key is required and that paging uses size and search_after. It lists the returned record fields and notes the scan uuid is provided for pulling the full report. It does not discuss rate limits or result caps, but adds meaningful context beyond the annotation set.

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 definition is front-loaded with purpose and query syntax, followed by return fields and use case. All three sentences carry information. The syntax list and paging mention are packed into a long compound sentence, slightly reducing readability.

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?

For a simple search tool with an output schema already present, the description covers everything an agent needs: query syntax, paging, authentication status, return fields, and intended questions. No material gap remains.

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%, so the description must carry the burden. It compensates substantially by giving query-field examples and explaining that size and search_after control paging. It does not explain search_after's accepted format (cursor vs. date, despite the example) or any bounds on size.

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 names a specific verb and resource: search the public urlscan.io archive of website scans. It also gives concrete query syntax examples (page.domain:, task.url, ip, asn, filename). It does not explicitly differentiate itself from urlscan_io_domain or urlscan_io_ip, so the sibling distinction has to be inferred.

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?

It clearly states the use case: answering which pages urlscan has already scanned for a domain, brand, or infrastructure indicator. It also notes no API key is needed, which removes a common usage question. It provides no explicit when-not-to-use guidance or named alternatives.

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.