Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

web_capabilities

Retrieve account web-retrieval limits and options: operations, crawl/research availability, max search results, map URLs, crawl pages, active jobs, render/sitemap modes, and query policies.

Instructions

Get web retrieval capabilities and limits. Returns the account's effective web retrieval limits and options: available_operations, crawl_available, research_available, search_max_results, map_max_urls, crawl_max_pages, max_active_jobs, and the accepted render_modes, sitemap_modes and query_policies. The operations list is empty while retrieval setup is incomplete.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description still discloses account-scoped behavior, enumerates the returned capability fields, and notes that the operations list is empty while retrieval setup is incomplete. It does not explicitly state read-only/no side effects, but 'Get' and zero parameters strongly imply a safe metadata read.

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?

Two sentences, front-loaded with the core purpose, followed by the returned fields and a useful setup caveat. The dense field list is necessary and there is no filler.

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?

No output schema exists, so the description carries the burden of explaining return values; it enumerates all the key returned fields and the setup-incomplete caveat. It omits field types and precise semantics, but is sufficient for a simple capability-check tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and an empty input schema, so the baseline is 4. The description appropriately does not waste space explaining parameters.

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: 'Get web retrieval capabilities and limits.' This clearly distinguishes it from retrieval-action siblings like web_scrape, web_search, and web_crawl, since this tool is a metadata/capability query.

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?

The purpose implies it should be used to discover account limits before retrieval, but the description does not explicitly say when to call it versus alternatives or state any prerequisites/exclusions.

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

Deploy Server

Other Tools