Skip to main content
Glama

List the account's website scans

list_website_scans
Read-onlyIdempotent

The website projects of this account with their scans, newest first: id, site, status, pages analysed, bytes saved. Reads only.

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_website_scans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Reads only' adds no new information and is largely redundant. What does add value beyond the structured fields is the 'newest first' ordering guarantee and the disclosure of which fields come back. Nothing is said about result size, pagination or truncation for an account-wide listing, which is the main behavioral unknown left.

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?

A single front-loaded sentence with a colon-delimited field list, which is an efficient structure for this kind of positional listing. The trailing 'Reads only' is the one redundant clause, since that is already conveyed by the annotations, but it costs almost nothing.

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 inputs, no output schema and full annotation coverage, the description carries the remaining burden of describing the return shape, which it does by naming the fields and the sort order. It is close to complete; the only gap is the absence of any hint about result volume or whether the response is capped.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema is an empty object, so the description cannot and need not add anything further here.

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 resource (the account's website projects and their scans) and enumerates the returned fields (id, site, status, pages analysed, bytes saved), which lets an agent distinguish this bulk-listing tool from the single-record get_website_scan and from list_website_pages/list_website_assets. It stops short of explicitly contrasting itself with those siblings, and it is phrased as a noun phrase rather than a verb, so it is clear but not maximally sharp.

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: the tool takes no parameters, so calling it to enumerate all scans is obvious, and 'Reads only' signals it is safe to call freely. There is no explicit statement of when to prefer it over get_website_scan or get_website_report, and no exclusions or preconditions are given, leaving routing entirely to inference.

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