Skip to main content
Glama
Sign In

Landfall

by io.github.landfall-audit
OverviewDiscussionsAdmin

Audit a landing page for paid ads (paid)

audit_landing_page
Read-onlyIdempotent

Audit a landing page before sending paid ad traffic. Returns a 0-100 readiness score, a ready / fix_first / not_ready verdict, Meta, Google and TikTok tags with IDs, conversion paths (forms, click-to-call, WhatsApp, booking), trust and speed facts, and the top 5 fixes in priority order. Costs 0.05 USDC per completed call, paid automatically via x402 if your client supports it. Never charged if the call fails.

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": {
      "url": "<url>"
    },
    "name": "audit_landing_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the page or website
keywordNoOptional ad keyword or headline to check message match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) URL of the landing page, e.g. https://example.com/offer"New value: +"Public http(s) URL of the page or website"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent), and the description layers on genuinely new operational facts: a 0.05 USDC cost per completed call, automatic x402 payment, and — critically — that failed calls are never charged. That cost/charging behavior is exactly the kind of trait structured fields cannot express.

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 return shape, then pricing. The middle enumeration of return values is long but each item is informative. No filler sentences, though the output list could be tightened.

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?

With no output schema, the description correctly carries the return contract (0-100 score, verdict values, tag detection, conversion paths, top 5 fixes), so an agent knows what it gets. It also covers cost and refund behavior. Minor gaps remain around latency/pagination, but the essential contract is present.

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 both parameters (url, keyword) are already documented in the schema. The description adds no syntax, format, or interpretation detail for either parameter, so the baseline 3 applies.

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?

States a specific verb and resource ("Audit a landing page") plus a concrete scope ("before sending paid ad traffic"). It does not name or distinguish itself from the close siblings preview_landing_page or sample_audit, so an agent must infer the difference.

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?

Gives a clear usage trigger — run it before spending on paid traffic — which tells the agent when this tool is relevant. It offers no exclusions or explicit routing to alternatives such as preview_landing_page or sample_audit, which would be valuable given the sibling set.

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

All Landfall toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources