Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

web_search

Search the public web. Search Brave's public web results. limit (1-50, default 10) is honoured by reading up to 3 result pages; each successful result page read costs 3 credits, and optional page reads (5 credits each) remain scoped to…

Instructions

Search the public web. Search Brave's public web results. limit (1-50, default 10) is honoured by reading up to 3 result pages; each successful result page read costs 3 credits, and optional page reads (5 credits each) remain scoped to each result host. country and language select the result locale (defaults us and en-us).

Input Schema

NameRequiredDescriptionDefault
requestYesSearch request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real behavioral context: the page-read mechanics for 'limit' and the credit costs (3 credits per page read, 5 per optional page read). It does not disclose auth requirements, rate limits, or what a result/response looks like, so it remains partial.

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

Conciseness3/5

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

The purpose is front-loaded, but the first two sentences are redundant ('Search the public web' / 'Search Brave's public web results'), and the credit/paging details make it dense without adding proportional value.

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?

For a nested-parameter search tool with no output schema and no annotations, the description covers the cost model and locale defaults adequately, but omits return shape, authentication, and how it relates to its many search siblings.

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 the nested properties (limit, country, language, etc.) are already documented. The description largely restates the limit and locale semantics that the schema conveys, adding only marginal value such as the host-scoping of optional page reads.

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 ('Search the public web', 'Brave's public web results'), so the agent knows exactly what it does. However, it does not differentiate itself from the many sibling search tools (notably brave_search, brave_news, brave_images), and the first two sentences are essentially the same statement.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no reference to alternatives. Given the enormous sibling list including brave_search and web_scrape, the absence of any routing signal (e.g. when to prefer this over brave_search or web_scrape) is a real gap.

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