Webanto

Inspect saved customer internal-link health

webanto_get_internal_link_report

Read-onlyIdempotent

Read one organization-owned saved crawl and bounded orphan-page results. Omit crawl_id for the latest completed crawl. Missing and unfinished crawls are explicit; saved counts and timestamps are not a fresh crawl or live page verification. Source-entry changes since a page was crawled are flagged. Private/query-bearing URLs are unavailable. No Webanto platform-blog mesh, page bodies, crawl launch, inference or provider calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "webanto_get_internal_link_report"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Opaque next_cursor from the preceding live page with the same filters; omit for the first page.
`crawl_id`	No	Exact saved organization crawl, or omit for its latest completed crawl. No crawl is started.
`page_size`	No	Maximum records in this page; at most 20.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing what the data actually represents: saved counts and timestamps are stale snapshots, source-entry changes since crawl time are flagged, private and query-bearing URLs are excluded, and no crawl is launched or provider call made. These are exactly the caveats an agent needs before treating the output as ground truth.

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-loads the core action in the first sentence, then packs caveats into dense clauses with no filler. The final fragment ('No Webanto platform-blog mesh, page bodies, crawl launch, inference or provider calls') is telegraphic but still conveys real scope limits.

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?

An output schema exists, so return values need not be explained, and the description still covers staleness, missing/unfinished crawls, pagination bounds, and unavailable URL classes. The main omission is any pointer to the sibling tool an agent should use instead when it wants suggestions rather than a saved report.

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%, so cursor, crawl_id, and page_size are already documented in structured fields. The description restates the crawl_id omission behavior but adds no new syntax or format meaning beyond the schema, which is the expected baseline here.

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: read one organization-owned saved crawl plus bounded orphan-page results. It implicitly separates itself from the suggestions-style sibling by emphasizing 'saved crawl' and 'saved counts' rather than live analysis, but it never names the alternative tool, so the differentiation requires inference.

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

Usage Guidelines3/5

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

Gives one concrete usage rule (omit crawl_id to get the latest completed crawl) and warns that saved counts are not a fresh crawl or live verification, which implies when not to rely on it. It offers no explicit routing guidance versus webanto_list_internal_link_suggestions or the other internal-link-related siblings.

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

All Webanto 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?