Skip to main content
Glama

GetBotRank Free AI Search Tools

view_as_crawler

view_as_crawler

Show the text and structure an AI crawler recovers from a page without running JavaScript.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL, for example https://example.com/page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the most important behavioral trait — no JavaScript execution, meaning JS-injected content will be absent from results — but says nothing about whether the fetch is live or cached, how redirects/robots are handled, or any limits on page size or request rate.

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?

One sentence, front-loaded with the action and ending on the most decision-relevant constraint (no JavaScript). Nothing is redundant or padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one URL in, read-only) but there is no output schema, so the description is the only source for what comes back; 'text and structure' is vague about format, and there is no mention of how the crawler is identified or what user-agent is simulated. Adequate for a quick check, but not fully self-contained.

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?

There is a single required parameter and schema description coverage is 100%, with the schema already giving a full-URL example. The description adds no meaning beyond that, which is acceptable at full coverage but is not additive.

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?

The description names a specific verb and resource (show the text and structure an AI crawler recovers from a page) and adds the key qualifier 'without running JavaScript,' which separates it from rendering-oriented siblings like check_rendering. It never names an alternative tool explicitly, so an agent must infer the boundary rather than read it.

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?

Usage is only implied: an agent can guess this is for auditing how a non-JS crawler sees a page, but there is no stated when-to-use, no when-not-to-use, and no pointer to check_rendering or check_ai_crawler_access for comparison. The scope note about JavaScript is the only routing signal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.