Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_report_schedules

List automated recurring report schedules configured on a property, including each report's ID, name, owner, delivery period, and recipient user IDs.

Instructions

List the reports configured for automated recurring delivery on a property — each with id, name, owner, period (week or month) and the recipient user IDs. Reflects the stored schedule configuration (period + recipients). 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_report_schedules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.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 mostly does: it states what the response contains (id, name, owner, period, recipient user IDs), clarifies that it reflects stored configuration, and discloses cursor pagination via next_cursor. It does not state read-only semantics explicitly, permission requirements, or any default page size.

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?

Three sentences, front-loaded with the resource definition, with no filler. The second sentence partially restates the field list from the first (period and recipients appear twice), which is mild redundancy but also reinforces that the data is stored config rather than computed output.

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?

There is no output schema, so the description correctly enumerates return fields and notes pagination, which covers most of what an agent needs for a zero-argument list tool. The gap is the cursor mechanism and property scoping: with an empty input schema, the agent cannot tell how next_cursor is passed back in or where the property is specified.

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?

Parameter count is zero, so the baseline would be 4, but the description introduces two undocumented inputs — 'on a property' and a cursor — while the schema exposes no properties and only additionalProperties=true. An agent is left unsure how the property scope or the next_cursor value is supplied, which is meaning that the schema does not resolve.

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 uses a specific verb ('List') on a well-defined resource ('reports configured for automated recurring delivery on a property') and enumerates the returned fields. It implicitly separates itself from list_reports by emphasizing schedule configuration rather than report content, but never names or explicitly contrasts the sibling.

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 agent can infer this is the tool for inspecting delivery schedules rather than report output. There is no explicit when-to-use, no mention of when list_reports or get_report would be the better choice, and no prerequisites stated.

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