Skip to main content
Glama

Black SEO Analyzer

list_crawls

Read-only

List the crawl sessions stored for this account, newest last, with their session_id, start URL, start and end times, and page count. Single-page checks made with check_page are not crawls and are not listed. Call this first when the user refers to "the last crawl" or when you need a session_id for issues_summary, query_issues, page_report or compare_crawls. A session with no end time is still running or was interrupted.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/non-open-world, and the description adds real context beyond them: result ordering, the field set returned, the check_page exclusion, and the interpretation rule that a missing end time means running or interrupted. It stops short of saying anything about result size or limits for accounts with many sessions, which is the one remaining behavioral unknown.

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 sentences, each load-bearing: what it returns, what it excludes, when to call it, and how to read an incomplete session. Scope and field list are front-loaded before the routing guidance.

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?

With no output schema, the description compensates by enumerating the returned fields, and with no parameters there is nothing else an agent needs before calling. The check_page exclusion and the no-end-time interpretation cover the two likely sources of misuse.

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 meaning to add and the baseline of 4 applies. The description correctly spends no words on arguments.

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 and resource ("List the crawl sessions stored for this account") plus the exact fields returned (session_id, start URL, start/end times, page count) and ordering ("newest last"). It also explicitly excludes single-page checks made with check_page, so the boundary against that sibling is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives a concrete trigger ("Call this first when the user refers to 'the last crawl'") and names the downstream consumers that need a session_id: issues_summary, query_issues, page_report, compare_crawls. It also states a when-not condition via the check_page exclusion, leaving nothing 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.