Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Audit Tool

adataforseo.audit

Read the latest SEO audit, coverage, and research findings as effect-sorted cards showing what is wrong, why it matters, fix code, and affected URLs with issue IDs.

Instructions

Read-only. The findings of the latest coverage, audit and research runs as cards sorted by expected effect: what is wrong, why it matters, the fix code and up to 8 affected URLs with issue ids.

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": "adataforseo.audit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It discloses read-only status, latest-run scope, sorting by expected effect, and an up-to-8-URL limit, but it omits permissions, pagination or empty-state behavior, and freshness details.

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?

The description is short and front-loads 'Read-only,' then gives a dense but useful sentence about the returned cards. It is concise with little waste, though the long sentence could be slightly easier to scan.

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?

There is no output schema, so the description must explain return values, and it does so by listing card fields and the URL limit. It does not cover edge cases or the relationship to apply_fix, but it is adequate for a zero-parameter read-only tool.

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 tool has zero parameters, so there is no parameter meaning to add beyond the schema. The baseline for a zero-parameter tool is 4.

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 states that the tool returns findings from the latest coverage, audit, and research runs, and it enumerates the card contents, so the resource and output are clear. It does not explicitly contrast itself with sibling tools such as coverage or apply_fix, so it falls short of 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 when-to-use or when-not guidance. 'Read-only' and 'latest' imply inspection, but the description does not tell the agent when to choose this over coverage or apply_fix, and it names no alternatives.

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