nimo

Read SEO Evidence

get_seo_evidence

Read-onlyIdempotent

START HERE for SEO recommendations, page optimization, noindex/robots verification, organic traffic or source comparisons. Read SEO evidence for one owned page, with source, scope, units and limitations. Use refresh:true sources:[page] to verify deployed HTML. GSC data is search analytics only; select indexing (page scope) for Google's URL Inspection index status. Saved by default. For a requested diagnosis use freshness:missing to recover absent Google/page evidence without paid Ahrefs reads, or freshness:fresh for explicit live reads. Use scope:site for the exact owned origin; dates, comparePrevious, dimension, limit and offset support search diagnosis. Select backlinks (freshness:fresh, uses Ahrefs allowance) for live referring domains and backlinks to the page, or to the host with scope:site. Select discovery for crawler/content evidence and aiReferrals for GA4 attributed AI sessions (not recommendations). No audits, publication or edits. GSC clicks, GA4 sessions/users and Ahrefs estimates must never be added or relabeled. Empty performance recommendations do not prove technical SEO health. For site-wide sitemap coverage, pages without impressions and duplicate content use get_search_coverage.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum search rows to return (1–100)
`scope`	No	Page URL or exact owned site origin	page
`offset`	No	Search row pagination offset
`siteId`	Yes	Owned Nimo site ID from list_sites
`auditId`	No	Owned saved audit to inspect; omit for latest. Cannot combine with refresh.
`endDate`	No	Inclusive end date, YYYY-MM-DD
`pageUrl`	No	Exact page on the selected site's origin. Defaults to the site's URL.
`refresh`	No	False reuses saved evidence without provider calls. True reads selected providers/page; Ahrefs may consume its allowance. Only refresh when requested.
`sources`	No	Evidence providers to include; fresh ahrefs or backlinks requires Ahrefs allowance authorization
`dimension`	No	Search analytics grouping	query
`freshness`	No	saved is default. missing refreshes absent selected Google/page/discovery evidence without paid Ahrefs calls. fresh reads selected sources; selecting ahrefs or backlinks authorizes Ahrefs allowance use.
`startDate`	No	Inclusive start date, YYYY-MM-DD
`includeSpam`	No	backlinks only: keep referring domains and backlinks Ahrefs flags as spam. Excluded by default so genuine links are not crowded out.
`comparePrevious`	No	Include the preceding matching-length window
`discoveryDetail`	No	summary returns robots.txt and llms.txt status, size and declared sitemaps; full adds their text.	summary

Output Schema

Name	Required	Description	Default
`mode`	Yes
`rules`	Yes
`siteId`	Yes
`status`	Yes
`auditId`	Yes
`pageUrl`	Yes
`sources`	Yes
`nextAction`	Yes
`retrievedAt`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent, but the description adds cost and side-effect detail beyond them: Ahrefs allowance is consumed by fresh ahrefs/backlinks/refresh reads, saved evidence is reused by default, and clicks/sessions/estimates 'must never be added or relabeled'. That is materially useful behavioral context an agent cannot get from the annotation block.

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

Conciseness3/5

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

Front-loaded with 'START HERE' and the core purpose, so an agent gets the gist immediately. But it is a dense ~170-word run-on paragraph whose sentences blend routing, parameter semantics and caveats, and it partly restates schema-level freshness/refresh semantics rather than only adding new information.

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?

For a 15-parameter read tool with an output schema (so return values need not be explained), the description covers purpose, routing, cost of refresh, source selection, scope semantics and interpretation pitfalls ('Empty performance recommendations do not prove technical SEO health'). Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, and the description does add real meaning for key parameters: it pairs refresh:true with sources:[page] for HTML verification, distinguishes freshness:missing from fresh by cost, and clarifies scope:site means the owned origin. It still leaves a few parameters (dimension, comparePrevious, offset, discoveryDetail) to the schema alone.

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 and resource ('Read SEO evidence for one owned page, with source, scope, units and limitations') and explicitly positions itself as the 'START HERE' entry point for SEO work. It names the sibling it is not (get_search_coverage for site-wide sitemap coverage, pages without impressions, duplicate content), letting an agent route without opening either schema.

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?

Gives explicit when-to-use branches: refresh:true sources:[page] to verify deployed HTML, freshness:missing to recover absent evidence without paid Ahrefs reads, freshness:fresh for live reads, scope:site for the exact owned origin, backlinks for referring domains. It also states exclusions ('No audits, publication or edits') and a concrete alternative (get_search_coverage).

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

All nimo tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.