Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_site_audit_projects

List a property's crawler projects and their audit_ids to target a specific crawl configuration. Use it to find the project ID, status, and latest health score before running audits.

Instructions

List the property's Crawler projects (crawl configurations) to find the audit_id to target. Each returns audit_id, name, mode (list / complete / organic_traffic), device, start_urls, status, progress, last_crawl_date, pages_crawled and the latest health_score. Most other Crawler tools default to the most recently finished crawl, so you only need this to target a specific project.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.7/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 largely succeeds: it enumerates the returned fields, discloses the mode enum values (list / complete / organic_traffic), and explains the default-crawl behavior of sibling tools, which is genuinely useful context beyond the schema. It omits anything about read-only guarantees, pagination, or whether all projects are returned in one call, leaving minor gaps for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with the verb and resource, then the field list, then the routing guidance. Every clause carries information — the field enumeration and the sibling-default note both earn their place.

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?

No output schema exists, so the description supplies the return contract itself via the field list, and with no parameters or annotations there is little else an agent needs. An agent can decide whether to call this tool and interpret its output from the description alone.

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?

There are zero input parameters, so the baseline is 4 and there is nothing parameter-level the description needs to compensate for. It correctly spends no words on parameter documentation.

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 property's Crawler projects (crawl configurations)") and adds the concrete goal — finding the audit_id to target. The parenthetical disambiguates 'projects' from ordinary SEO projects, and the enumerated return fields make the tool's identity unmistakable against siblings like list_site_audit_issues.

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?

Explicitly says when NOT to call it: most other Crawler tools default to the most recently finished crawl, so this is only needed to target a specific project. That is a concrete alternative-plus-condition statement, not merely implied usage.

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

Deploy Server

Other Tools