Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_reports

List SEO reports built for a property, including id, name, template and automation status. Returns plain reports by default; pass templates: true to list report templates instead.

Instructions

List the SEO Reporting reports built for a property — each with id, name, is_template, is_automate, created_at and owner. Returns plain reports by default; pass templates: true to list report templates instead. Recurring reports are excluded (use list_report_schedules). Cursor-paginated via next_cursor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose real behavior: default vs. template mode, exclusion of recurring reports, and cursor pagination via next_cursor. It stops short of stating permission or scope requirements (e.g., which property the reports are scoped to), which leaves a residual gap for a multi-tenant reporting API.

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 tight sentences: the default/scope statement comes first, then the mode switch, then the exclusion and pagination mechanics. No filler, no repetition of the tool name, and each sentence adds a distinct operational fact.

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?

The absence of an output schema is offset by the explicit field list, and pagination and sibling routing are covered. The one unresolved item is how the 'property' scope is determined, which an agent would need in order to invoke this correctly in a multi-property context.

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 input schema is effectively empty (additionalProperties: true, zero declared params), so the description is the only source of parameter meaning — and it supplies the `templates` boolean with its effect and `next_cursor` as the pagination handle. It does not explain the next_cursor format or how the target property is specified, so it is good but not complete.

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 SEO Reporting reports built for a property") and immediately enumerates the returned fields (id, name, is_template, is_automate, created_at, owner). It also distinguishes itself from the closely-named sibling list_report_schedules, so an agent can identify it without opening the schema.

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 explicit branch conditions: default behavior returns plain reports, `templates: true` switches to report templates, and recurring reports are excluded with a named alternative (list_report_schedules). This is a genuine when/when-not/alternative mapping rather than 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