Crawlora MCP

web_search

Read-only

Search the web for any topic or question and return ranked Brave results with title, URL, and snippet, optionally retrieving a bounded number of selected pages. Use this as the general-purpose web search tool; use a platform's own search tool, such as youtube_search or reddit_search, for site-specific results. limit (1 to 50, default 10) is honoured by reading up to 3 result pages, at 3 credits per result page read; country (default us) and language (default en-us) select the result locale. Results include partial source coverage and exact observed work usage.

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": {
      "q": "<q>"
    },
    "name": "web_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes
`limit`	No	Maximum results to return, 1 to 50; default 10. Larger limits read up to 3 result pages (3 credits per page read).
`scrape`	No
`country`	No	Result country, default us. Allowed values: all, ar, at, au, be, br, ca, ch, cl, cn, de, dk, es, fi, fr, gb, gr, hk, id, in, it, jp, kr, mx, my, nl, no, nz, ph, pl, pt, ru, sa, se, sg, tr, tw, us, za.
`language`	No	Result language, default en-us. Allowed values: de-de, en-ca, en-gb, en-in, en-us, fi-fi, fr-ca, fr-fr, ja-jp, pt-br, sq-al, sw-ke, zh-tw.
`max_credits`	No
`scrape_limit`	No
`exclude_domains`	No
`include_domains`	No

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 10, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Result country, default us. Allowed values: all, ar, at, au, be, br, ca, ch, cl, cn, de, dk, es, fi, fr, gb, gr, hk, id, in, it, jp, kr, mx, my, nl, no, nz, ph, pl, pt, ru, sa, se, sg, tr, tw, us, za.",
+  "type": "string"
+}

addedInput schema / properties / language

Added value: +{
+  "description": "Result language, default en-us. Allowed values: de-de, en-ca, en-gb, en-in, en-us, fi-fi, fr-ca, fr-fr, ja-jp, pt-br, sq-al, sw-ke, zh-tw.",
+  "type": "string"
+}

addedInput schema / properties / limit / description

Added value: +"Maximum results to return, 1 to 50; default 10. Larger limits read up to 3 result pages (3 credits per page read)."

AddedOct 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral cost context (limit is honoured by reading up to 3 result pages at 3 credits per page read) and caveats about partial source coverage and observed work usage. The final clause is vague, keeping it short of a 5.

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?

Three dense sentences with routing guidance front-loaded, then return shape, then parameter/cost semantics. No filler despite covering a lot.

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?

Output schema exists so return values need no elaboration, and annotations carry the safety profile. The main gap is the undocumented scrape/credit/domain-filter parameters, which an agent would need to reason about when tuning a call.

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 only 33% across 9 parameters. The description documents limit (range, default, credit cost), country, and language defaults, which is genuinely useful, but scrape, max_credits, scrape_limit, exclude_domains, and include_domains get no explanation anywhere. Baseline 3 for partial compensation.

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+resource ('Search the web') plus the return shape (ranked Brave results with title, URL, snippet) and the optional page retrieval. It also distinguishes itself from site-specific siblings like youtube_search and reddit_search.

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

Usage Guidelines5/5

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

Explicit routing guidance: 'Use this as the general-purpose web search tool; use a platform's own search tool, such as youtube_search or reddit_search, for site-specific results.' Both the when and the alternative are named.

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

All Crawlora MCP 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.