Skip to main content
Glama

seo_list_monitor_log

Retrieve paginated 404 monitor logs for a WordPress site, including URL, hit counts, and first/last seen dates. Filter by URL, sort by column, and control page size.

Instructions

List the 404 monitor log: { items: [{ id, url, hits, first_seen, last_seen, ... }], total, pages }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "seo_list_monitor_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
siteYesSite id (see list_sites)
orderNoSort direction (default DESC)
searchNoSubstring of the 404 URL
order_byNoSort column (default last_seen)
per_pageNoItems per page, 1-100 (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.14.0
    • addedInput schema / properties / order
      Added value: +{
      +  "description": "Sort direction (default DESC)",
      +  "enum": [
      +    "ASC",
      +    "DESC"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / order_by
      Added value: +{
      +  "description": "Sort column (default last_seen)",
      +  "enum": [
      +    "id",
      +    "url",
      +    "hits",
      +    "first_seen",
      +    "last_seen"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Page number (default 1)",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / params
      Removed value: -{
      -  "additionalProperties": {
      -    "type": [
      -      "string",
      -      "number"
      -    ]
      -  },
      -  "description": "Query params (page, per_page, search, ...)",
      -  "type": "object"
      -}
    • addedInput schema / properties / per_page
      Added value: +{
      +  "description": "Items per page, 1-100 (default 50)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Substring of the 404 URL",
      +  "type": "string"
      +}
  2. Addedv3.4.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does usefully disclose the response envelope (items array with id/url/hits/first_seen/last_seen, plus total and pages), which is valuable given there is no output schema, but it says nothing about read-only safety, permissions, pagination limits, or row volume.

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?

A single front-loaded sentence with zero preamble waste; the inline return shape earns its space because no output schema exists. Slightly dense but efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter filtered list tool with no annotations and no output schema, the description covers purpose and return shape but omits any relationship to the clearing/redirect-creation siblings and any hint about scoping to a required site. Adequate but with clear gaps.

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?

Schema description coverage is 100%, with enums and defaults documented inline, so the schema already does the heavy lifting. The description adds no parameter meaning beyond that, which matches the baseline 3.

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') plus a specific resource ('the 404 monitor log') and even sketches the returned fields, so an agent immediately knows this is a read of the 404 log. It does not explicitly distinguish itself from the related log siblings (seo_clear_monitor_log, seo_create_redirect_from_log), which keeps it below a 5.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus seo_clear_monitor_log or seo_create_redirect_from_log, and no stated prerequisites such as needing a site id. Usage is only implied by the word 'List'.

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