Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_code_monitor_change

Retrieve before and after values for a single detected site change by URL and timestamp, with type, property, and values per changed field. Filter by changeType to inspect one field.

Instructions

Get the before/after values for a single detected change, addressed by url + createdAt — one entry per changed field with type, property, before and after (arrays for multi-valued fields). Pass changeType to return just one field. Returns not_found when no change matches and invalid_change_type for an unknown field label.

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": "get_code_monitor_change"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/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 return shape (one entry per changed field with type, property, before and after, arrays for multi-valued fields) and names two concrete error outcomes, not_found and invalid_change_type. It omits any mention of read-only safety, permissions, or whether historical changes can be retrieved after some retention window.

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 dense sentences, front-loaded with the identification key before the optional filter and error codes. Every clause adds information an agent needs; nothing is redundant with the name or schema.

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?

No output schema and no annotations mean the description must explain returns and errors, which it does. The main residual gap is that the input schema is an empty object, so an agent gets no formal parameter names or types beyond what the prose implies, and format details for createdAt are unstated.

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 schema declares zero properties, so the description is the only source of parameter meaning, and it supplies three: url and createdAt as the composite address, and changeType as an optional single-field filter with an invalid_change_type failure mode. It does not specify the accepted format for createdAt or how changeType labels map to property names.

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?

"Get the before/after values for a single detected change" states a specific verb, resource, and cardinality, which distinguishes it from the plural sibling list_code_monitor_changes and from get_code_monitor_snapshot. The addressing key (url + createdAt) further pins down what identifies the one record.

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?

It gives clear context: use this to resolve one already-detected change by url + createdAt, and pass changeType to narrow to a single field. It stops short of explicitly telling the agent to call list_code_monitor_changes first to obtain those keys, so the discovery workflow is left implicit.

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