Skip to main content
Glama

seo_clear_monitor_log

Delete 404 monitor log entries by ID, date range, or clear the entire log when no filters are provided.

Instructions

Delete 404 monitor log entries: one entry by id, or every entry last seen within from..to (inclusive dates, either bound optional). With no argument the WHOLE log is cleared. Returns { deleted, success }.

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

Input Schema

NameRequiredDescriptionDefault
idNoDelete only this log entry
toNoDelete entries last seen on or before this date (YYYY-MM-DD)
fromNoDelete entries last seen on or after this date (YYYY-MM-DD)
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Delete entries last seen on or after this date (YYYY-MM-DD)",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Delete only this log entry",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Delete entries last seen on or before this date (YYYY-MM-DD)",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
  2. Addedv3.4.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the destructive blast radius (no argument clears the WHOLE log), the inclusive date semantics, and the return shape { deleted, success }. It does not state that deletion is irreversible or mention any required permission level, which are the main remaining behavioral gaps for a destructive tool.

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?

Tightly front-loaded: the destructive resource comes first, the addressing modes follow, and the return shape closes it out. Nearly every clause earns its place; the capitalized WHOLE is a well-placed emphasis rather than filler.

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 four-parameter destructive tool with no annotations and no output schema, the definition covers scope, argument combinations, and even the response fields, which is close to self-sufficient. The gaps are the lack of any irreversibility warning or permission prerequisite.

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 coverage is 100%, so all four parameters are already documented, giving a baseline of 3. The description adds genuine value by clarifying that date bounds are inclusive and individually optional, but it does not explain precedence when id is combined with from/to, so the added meaning is incremental.

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?

States a specific verb (Delete) and resource (404 monitor log entries), then enumerates the exact addressing modes: single id, date range, or whole-log. This is unambiguous and clearly distinct from the read-side sibling seo_list_monitor_log.

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?

Explains precisely when each parameter form applies (id for one entry, from/to for a date window, neither for the entire log) and flags the no-argument case explicitly. It does not name an alternative tool such as seo_list_monitor_log for inspecting entries first, so it stops short of full routing guidance.

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