Skip to main content
Glama

urlscan_search

Search urlscan.io scan records by domain, IP, URL, or filename to retrieve scan times, page metadata, server/ASN details, and result links without an API key.

Instructions

Search urlscan.io scans for a domain, IP, URL or filename (keyless).

Auto-prefixes plain domains with domain:, IPs with ip: and URLs with page.url:. Returns scan time, page metadata, server, ASN and result links.

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": {
      "query": "<query>"
    },
    "name": "urlscan_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: the '(keyless)' auth note and, importantly, the automatic query normalization (domain:, ip:, page.url:) that silently rewrites input. It omits rate limits, pagination behavior, and failure modes for a third-party scan API.

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?

Three short sentences, front-loaded with purpose, then the input-normalization rule, then the return shape. No filler, and each sentence conveys distinct information.

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 no annotations and no output schema, the description does a good job enumerating returned fields (scan time, page metadata, server, ASN, result links). The main remaining hole is the undocumented `limit` parameter and lack of pagination context.

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%, so the description must compensate. It explains the `query` parameter well, including the auto-prefix rules, but leaves `limit` entirely undocumented (no default, no maximum), and 'filename' is listed as accepted yet not covered by any prefix rule.

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 ('Search') and a specific resource (urlscan.io scans), plus the accepted query types (domain, IP, URL, filename). The resource is unique among the sibling search tools, so an agent can select it 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 Guidelines3/5

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

No explicit when-to-use/when-not guidance and no named alternatives among the many *_search siblings. Usage is only implied by the resource itself and the parenthetical '(keyless)', which hints that no API key is required.

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