Skip to main content
Glama

Urlscan Io Domain

urlscan_io_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.

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": {
      "domain": "example.com"
    },
    "name": "urlscan_io_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault
tookNoQuery execution time in milliseconds
totalNoTotal number of results for this domain
resultsNoArray of scan results for the domain
has_moreNoWhether more results are available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful operational detail that no API key is needed, but otherwise restates result fields that the output schema already provides. Nothing about result volume, recency window, or rate limits is disclosed.

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?

A single front-loaded sentence with the resource, scope, and the no-key constraint, plus a brief return-value clause. There is no redundant or filler wording.

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?

For a one-parameter, read-only search tool with an output schema and full annotations, the description covers purpose, scope, and access requirement adequately. The remaining gap is search semantics — result caps, time range, and domain-vs-URL input handling — which matters for a historical scan index.

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?

Only one parameter with 0% schema description coverage, so the description carries the burden; it clarifies that the parameter is a domain, implying a bare domain rather than a full URL. It does not state whether subdomains, wildcards, or paths are accepted, and the schema itself only offers an 'example.com' example.

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?

States a specific verb and resource ('Search urlscan.io past scan results') and scopes it to 'a specific domain', which naturally distinguishes it from the ip variant. It stops short of naming urlscan_io_search or explaining how a domain-scoped search differs from the general search sibling.

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?

Implies the use case (historical scan lookup for a domain) and notes that no API key is required, which is a real prerequisite-free signal. There is no explicit when-to-use/when-not guidance and no pointer to urlscan_io_ip or urlscan_io_search, leaving the agent to infer selection from the tool name.

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.