Site SEO & AI Crawler Audit

Check a landing page for conversion

landing_page_check

Read-onlyIdempotent

Checks a landing page for conversion problems. Use it when the user asks how to get more sign-ups, sales or enquiries from a landing page, for example "review https://example.com/ for conversion" or "does my landing page have a clear call to action?". Pass the page address. Returns twelve checks, each with a status, evidence and a fix: the h1 and the sentence under it, the primary call to action and its repeats, whether up to five call-to-action links work, form field count, trust signals, a visible price or next step, the viewport tag, HTML size, render-blocking hints and a contact path. It reads one page, tests a few links, skips what robots.txt disallows for Agent Tools, does not run JavaScript, and returns no page copy, reviews or contact details. It is a checklist, not a conversion forecast, a speed test or a design review. Do not use it for private or local addresses, rankings or traffic.

Input Schema

Name	Required	Description	Default
`url`	Yes	Address of one public landing page, for example https://example.com/. A bare domain such as example.com means https. Only public http and https sites on the standard ports are checked.

Output Schema

Name	Required	Description
`url`	Yes	The landing page address checked.
`asOf`	No	When the page was read, ISO 8601 UTC.
`page`	No
`notes`	No	Plain-language caveats to pass on with the result.
`notice`	Yes	As-of caveat: what the site sent to Agent Tools at that moment.
`source`	Yes	Where the data came from: the website itself.
`status`	No	HTTP status code of the final page.
`failure`	No	Why the page was not reached or read, such as a timeout or a robots.txt disallow for Agent Tools.
`summary`	No
`finalUrl`	No	Address of the page after redirects.
`findings`	No
`reachable`	Yes	False when the page was not reached; failure then says why.
`reference`	No	Where the checklist topics come from.
`requestsMade`	No	Requests made, the page and up to five call-to-action links.
`callsToAction`	No
`blockedByRobots`	No	True when robots.txt disallows the page for Agent Tools, so it was not requested.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 12, 2026

addedOutput schema / properties / asOf / description

Added value: +"When the page was read, ISO 8601 UTC."

addedOutput schema / properties / blockedByRobots / description

Added value: +"True when robots.txt disallows the page for Agent Tools, so it was not requested."

addedOutput schema / properties / failure / description

Added value: +"Why the page was not reached or read, such as a timeout or a robots.txt disallow for Agent Tools."

addedOutput schema / properties / finalUrl / description
```
Added value: +"Address of the page after redirects."
```
addedOutput schema / properties / findings / items / properties / evidence / description
```
Added value: +"What was found on the page."
```
addedOutput schema / properties / findings / items / properties / fix / description
```
Added value: +"What to change; absent on a pass."
```

addedOutput schema / properties / notes / description

Added value: +"Plain-language caveats to pass on with the result."

addedOutput schema / properties / notice / description

Added value: +"As-of caveat: what the site sent to Agent Tools at that moment."

addedOutput schema / properties / reachable / description

Added value: +"False when the page was not reached; failure then says why."

addedOutput schema / properties / reference / description
```
Added value: +"Where the checklist topics come from."
```

addedOutput schema / properties / requestsMade / description

Added value: +"Requests made, the page and up to five call-to-action links."

addedOutput schema / properties / source / description

Added value: +"Where the data came from: the website itself."

addedOutput schema / properties / status / description

Added value: +"HTTP status code of the final page."

addedOutput schema / properties / url / description

Added value: +"The landing page address checked."

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, open-world behavior, but the description adds substantial beyond-schema context: single-page scope, link testing, robots.txt compliance for Agent Tools, no JavaScript execution, and explicitly no page copy or contact details returned.

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?

Front-loaded with purpose and trigger, then scope, then exclusions. It is on the long side and the enumeration of twelve checks is dense, but nearly every clause carries usable 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?

Despite an output schema existing, the description adds the shape of the return (checks with status, evidence, fix), plus limits (no JS, one page, robots.txt). An agent has everything needed to decide and invoke correctly.

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 description coverage is 100% and the schema already documents the URL format, max length, and public http/https restriction, so the brief 'Pass the page address' adds nothing. Baseline 3 for a fully documented single 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?

States a specific verb and resource ('checks a landing page for conversion problems') plus the exact scope of output (twelve named checks), which cleanly separates it from siblings like product_page_seo and check_page_tags.

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 trigger phrasing examples ('review https://example.com/ for conversion') and explicit exclusions: not for private/local addresses, rankings, traffic, speed tests, or design reviews. It also names what the tool is not (a conversion forecast).

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

All Site SEO & AI Crawler Audit 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.