Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brave_videos

Search Brave video results by query, returning normalized JSON with country, language, pagination, and date filters for building video search features.

Instructions

Search Brave video results. Returns normalized Brave video search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Brave Search video HTML and return 503 when Brave serves a challenge page or unusable HTML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
langNoBrave UI language; defaults to en-us
countNoResults to return; defaults to 10, clamped to 1..50
offsetNoZero-based Brave result page; defaults to 0
countryNoBrave result country; defaults to us
date_toNoCustom end date in YYYY-MM-DD; requires date_from
date_fromNoCustom start date in YYYY-MM-DD; requires date_to
time_rangeNoPreset time filter: any, day, week, month, year, or custom

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / country / enum
      Added value: +[
+  "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"
+]
    • addedInput schema / properties / lang / enum
      Added value: +[
+  "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"
+]
    • addedInput schema / properties / time_range / enum
      Added value: +[
+  "any",
+  "day",
+  "week",
+  "month",
+  "year",
+  "custom"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses useful behavior: results are fetched from public Brave Search video HTML and may return 503 on challenge pages. This surfaces the source and a key failure mode. It does not mention rate limits or response format, but those are less critical for a read/search tool.

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?

Three sentences with the main action and resource front-loaded. The content is tight and informative, though it slightly repeats 'Brave video search results'.

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?

Covers the query parameter, locale defaults, and the 503 failure case, while the schema covers all parameters. However, with no output schema and no annotations, the structure of the 'normalized' results is left unspecified.

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 baseline is 3. The description adds locale default context (country=us, lang=en-us) but does not elaborate on count/offset/date parameters, which the schema already documents.

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 'Search Brave video results' and clarifies that it returns normalized Brave video search results for a query string. The video resource is clear and distinguishable from Brave search/news/image siblings, though no explicit sibling comparison is made.

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 description implies use for video search via 'Search Brave video results', but it does not state when to prefer this over alternatives like bing_videos or google_videos, nor does it give exclusions. An agent can infer usage but gets no routing guidance.

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