Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List ignored audit findings

audits_ignored
Read-onlyIdempotent

The site audit findings people chose to ignore, newest first. They do not show in seo_get_audit_issues.

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": {
      "siteId": "<siteId>"
    },
    "name": "audits_ignored"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered. The description adds genuine value beyond that with the newest-first ordering and the complement relationship to seo_get_audit_issues, but says nothing about pagination, result limits, or why findings were ignored.

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 short sentences, front-loaded with the resource and ordering, followed by the disambiguation clause. No filler and nothing that could be trimmed without losing meaning.

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 one-parameter read-only list tool with rich annotations and no output schema, the description covers what the tool returns, its ordering, and its relation to the sibling. The remaining gap is the undocumented siteId and absent pagination behavior, which is a modest shortfall given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required siteId parameter, so the schema provides no semantics at all. The description never mentions siteId or explains that results are scoped to one site; 'site audit findings' only weakly implies site scoping, leaving the parameter effectively undocumented.

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 identifies the exact resource (site audit findings that were ignored) and adds two distinguishing properties: sort order (newest first) and set exclusion versus seo_get_audit_issues. The verb is only implied ('The site audit findings...'), but an agent can immediately tell what this returns and how it differs from the sibling.

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?

The sentence 'They do not show in seo_get_audit_issues' functions as explicit routing guidance: if the agent wants the ignored subset, it must call this tool rather than the general issues tool. There are no stated prerequisites or exclusions beyond that, but for a simple list tool the when-to-use signal is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources