Skip to main content
Glama

SEO findings across sites

recipe__seo_findings
Read-onlyIdempotent

Every open Royal SEO Standard finding for one site, as the fixes to make in order: site-wide fixes first, then blockers, then by impact times the importance of the pages affected. Each fix has its sub-score, impact, a plain-English title, what it means, how to fix it, who usually makes it (settings, content, developer or host), whether it is site-wide, and up to 25 affected pages (URL and WordPress post_id, for fleet__update_seo_meta), most important first. Also returns the site's bands, how many findings are still being confirmed, problems the agency accepted or dismissed (with the reason a person wrote and any end date), findings fixed in the last 30 days, Search Console results, and page_checks (which of the site's own page checks ran, the saved Rank Math score per page on Rank Math sites, where a null score means not analysed yet, and SEObolt's AI search visibility score per page on SEObolt Pro sites). Reads Royally's stored results only. Muted problems still count in the bands. Use recipe__seo_audit for the fleet view and this tool to plan work on one site.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

While annotations handle safety, the description adds critical operational context not found elsewhere. It states the tool 'Reads Royally's stored results only,' which immediately informs the agent that this is a retrieval of historical data, not a live API call, a key behavioral trait.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is excessively long and densely packed, violating the principle of conciseness. It is structured as a comprehensive data contract or API documentation rather than a quick, front-loaded guide for an AI agent. The sheer volume of text is overwhelming.

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

Completeness5/5

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

Given the high complexity of the output (including bands, Search Console results, Rank Math scores, and specific workflow advice), the description provides an extremely thorough account of the data structure and content available.

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 coverage is 100%, so the description does not need to compensate. It successfully adds semantic value by defining the scope of the returned results relative to the single 'site_id' parameter.

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?

The description clearly defines the tool's purpose: retrieving 'Royal SEO Standard finding[s]'. It distinguishes this from 'run' tools by specifying that it retrieves 'Every open' finding, making the distinction between planning (this tool) and execution (siblings) clear.

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

Usage Guidelines5/5

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

The guidance is explicit, instructing the agent: 'Use recipe__seo_audit for the fleet view and this tool to plan work on one site.' This is a definitive guide for tool selection based on operational scope.

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