LandingBoost

Suggest pages to scan

suggest_pages

Read-only

Pages worth scanning on a website, from its sitemap and homepage links: homepage, pricing, features, comparison and other first-level pages, each with its role and where it was found. recommended=true marks the default pick (homepage and pricing). Free and does not count toward the scan limit. Pass the chosen URLs to scan_site as pages.

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": "suggest_pages"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Homepage URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral context beyond annotations: results come from sitemap and homepage links, recommended=true marks defaults, and the call is free with no scan-limit impact.

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

Conciseness5/5

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

The description is compact and front-loaded: it first defines what the tool returns, then explains the recommended flag, then covers cost and the handoff to scan_site. Every sentence contributes useful selection or invocation context.

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 one-parameter, read-only suggestion tool with no output schema, the description explains the returned page roles, discovery provenance, default recommendations, cost behavior, and next step. Nothing essential for correct invocation appears missing.

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 coverage is 100% and the single url parameter is already documented as 'Homepage URL'. The description reinforces that the input is a website homepage, but adds no additional syntax, constraints, or format details beyond the schema baseline.

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 states a specific resource and output: pages worth scanning from a website's sitemap and homepage links, including page roles and discovery locations. It also distinguishes the tool from scan_site by telling the agent to pass chosen URLs to scan_site as pages.

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?

The description gives clear workflow context: use this to get recommended scan candidates, then pass chosen URLs to scan_site. It does not explicitly cover when not to use it versus scan_site or recheck_page, but the intended usage is clear.

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

All LandingBoost tools Inspect

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

Need Help?