Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_code_monitor_pages

Lists a property's Code Monitor pages with URL, last-change time, and change count, with URL-substring filtering and cursor pagination.

Instructions

List the pages a property tracks in Code Monitor, each with its monitoring status — url, last_change_at (most recent detected change) and changes_count (total changes detected). Filter by url substring; cursor-paginated (limit max 200). Returns feature_not_available when the plan doesn't include Code Monitor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/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 does well: it discloses the returned fields and their meaning, the pagination model ('cursor-paginated') with a limit cap of 200, and a plan-gated error response (feature_not_available). It omits permission/auth requirements and whether pagination returns a next-cursor token, which keeps it out of the top band.

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 compact sentences, front-loaded with the core purpose and followed by output fields, filtering/pagination, and the error case. No filler, though the field list in the first sentence is dense and could be split for readability.

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?

Because there is no output schema, listing the returned fields is essential and is done here; the pagination cap and plan-gated error are also covered. Remaining gaps are minor: no indication of sort order, default page size, or what a cursor value looks like.

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 an empty object, yet the description documents the operative inputs: filtering by url substring, cursor pagination, and a maximum limit of 200. This meaningfully compensates for a schema that declares no properties, though it doesn't state whether url match is case-sensitive or what the default limit is.

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?

The description opens with a specific verb and resource ('List the pages a property tracks in Code Monitor') and enumerates the returned fields (url, last_change_at, changes_count), which clearly separates it from list_code_monitor_changes and get_code_monitor_snapshot. An agent can identify the tool's output shape from the description alone.

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 implied by the scope statement ('pages a property tracks') and by the note that it returns feature_not_available when the plan lacks Code Monitor, which effectively tells the agent when the call will fail. However, there is no explicit when-to-use/when-not guidance and no named alternative for retrieving change-level or snapshot-level data.

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