Skip to main content
Glama

List scans

list_scans
Read-only

List monitoring scans: each scan is one kind-scoped check of a monitor's sources (domains, trademarks, apps or search ads). Shows when monitoring last checked, what it found, and any asset failures.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based. Page size is 50.
sinceNoISO 8601 date or datetime; only scans started on/after this time.
monitor_idNoLimits results to one monitor.

Output Schema

NameRequiredDescriptionDefault
pageYes
scansYes
totalYes
page_sizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / scans / items / properties / failures / items / properties / type / enum
      Previous value: -[
      -  "domain",
      -  "trademark",
      -  "app"
      -]New value: +[
      +  "domain",
      +  "trademark",
      +  "app",
      +  "search_ad"
      +]
    • changedOutput schema / properties / scans / items / properties / kind / enum
      Previous value: -[
      -  "domain",
      -  "trademark",
      -  "app"
      -]New value: +[
      +  "domain",
      +  "trademark",
      +  "app",
      +  "search_ad"
      +]
  2. Changed2 schema fields changed
    • removedOutput schema / properties / scans / items / properties / id
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / scans / items / required
      Previous value: -[
      -  "id",
      -  "monitor_id",
      -  "kind",
      -  "status",
      -  "started_at",
      -  "asset_count",
      -  "sources_summary",
      -  "is_initial",
      -  "matches_total",
      -  "new_matches",
      -  "reappeared_matches",
      -  "pending_assessment",
      -  "failures",
      -  "dashboard_url"
      -]New value: +[
      +  "monitor_id",
      +  "kind",
      +  "status",
      +  "started_at",
      +  "asset_count",
      +  "sources_summary",
      +  "is_initial",
      +  "matches_total",
      +  "new_matches",
      +  "reappeared_matches",
      +  "pending_assessment",
      +  "failures",
      +  "dashboard_url"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / monitor_id / description
      Previous value: -"Restrict to one monitor."New value: +"Limits results to one monitor."
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds conceptual context (a scan is a per-monitor kind-scoped check) and hints at the returned content, but discloses no cost, rate-limit, or ordering behavior beyond that.

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?

Two tight sentences with no filler, and the definition of a scan is front-loaded right after the verb. The second sentence on returned content could be trimmed since an output schema exists, but it is not wasteful.

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 strong annotations and a full output schema, the description only needs to orient the agent, which it does by explaining the scan concept and the pagination/filter surface. Nothing critical is missing, though ordering (newest first?) and default page behavior are unstated.

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% with three well-documented params including page size (50), ISO 8601 since semantics, and monitor_id scoping. The description adds nothing about parameters, so the baseline 3 applies — the schema does all the work.

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?

Specific verb (List) plus resource (monitoring scans), and it goes further by defining what a scan actually is: one kind-scoped check of a monitor's sources. An agent knows this returns scan history, not monitor config or matches, though it never names the sibling tools it differs from.

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?

Usage is only implied by the noun phrase "monitoring scans"; there is no explicit statement of when to reach for this versus list_monitors, list_matches, or summarize_matches. The agent can infer it is the historical/audit view, but must do the routing work itself.

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.

Resources