Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_code_monitor_changes

List detected on-page code and HTML changes newest first, filtered by page, project, or date range, to review SEO-relevant updates like titles, canonicals, meta descriptions, and status codes.

Instructions

List detected on-page code/HTML changes, newest first — each with url, date and change_types (Title, Canonical, Meta Description, noindex, robots.txt, sitemap.xml, H1, Status code, Hreflang, Open Graph, Twitter image, Analytics, Tag Manager). Filter to one page with seoMonitorId or page, or omit for the project-wide recent-changes feed; narrow with from/to. Cursor-paginated (limit max 200).

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

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 supplied, the description carries the full behavioral burden and does reasonably well: it discloses newest-first ordering, cursor-based pagination, and a hard limit cap of 200. It does not mention permission requirements, rate limits, or what happens when from/to values are malformed.

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: purpose and ordering first, then the filter decision, then pagination constraints. The long parenthetical enumeration of change types is dense but earns its place because no output schema exists to convey what each record contains.

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?

For a tool with no annotations, no output schema, and an empty parameter schema, the description supplies the return shape, the filtering model, and pagination behavior — enough to call it correctly. Gaps remain around date input format and cursor syntax, which an agent would have to guess.

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 with additionalProperties true, so the description is the only source of parameter meaning, and it names seoMonitorId, page, from/to, and the limit ceiling with their roles. It omits date format for from/to and the exact cursor parameter name, which leaves minor ambiguity for actual invocation.

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?

States a specific verb and resource: 'List detected on-page code/HTML changes', and enumerates the change types included (title, canonical, meta description, noindex, robots.txt, and so on), which makes the scope unambiguous. It implicitly separates the project-wide feed from a single-page view but never names a sibling such as get_code_monitor_change for drilling into one change, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

'Filter to one page with seoMonitorId or page, or omit for the project-wide recent-changes feed; narrow with from/to' gives clear when-to-use context and even offers two alternative parameters for the same narrowing. It stops short of explicit exclusions, such as directing the agent to get_code_monitor_change for full change detail or list_code_monitor_pages to discover valid monitor IDs.

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