Skip to main content
Glama
brave

Brave Search MCP Server

Official
by brave
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Remote

brave_video_search

brave_video_search

Search for videos by keyword or topic to get structured results with title, URL, description, duration, and thumbnail metadata.

Instructions

Searches for videos using Brave's Video Search API and returns structured video results with metadata.

When to use:
    - When you need to find videos related to a specific topic, keyword, or query.
    - Useful for discovering video content, getting video metadata, or finding videos from specific creators/publishers.

Returns a JSON list of video-related results with title, url, description, duration, and thumbnail_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results (1-50, default 20). Combine this parameter with `offset` to paginate search results.
queryYesThe user's search query. Query cannot be empty. Limited to 400 characters and 50 words.
offsetNoPagination offset (max 9, default 0). Combine this parameter with `count` to paginate search results.
countryNoSearch query country, where the results come from. The country string is limited to 2 character country codes of supported countries.US
ui_langNoUser interface language preferred in response. Usually of the format <language_code>-<country_code>. For more, see RFC 9110.en-US
freshnessNoFilters search results by when they were discovered. The following values are supported: 'pd' - Discovered within the last 24 hours. 'pw' - Discovered within the last 7 days. 'pm' - Discovered within the last 31 days. 'py' - Discovered within the last 365 days. 'YYYY-MM-DDtoYYYY-MM-DD' - timeframe is also supported by specifying the date range (e.g. '2022-04-01to2022-07-30').
safesearchNoFilters search results for adult content. The following values are supported: 'off' - No filtering. 'moderate' - Filter out explicit content. 'strict' - Filter out explicit and suggestive content. The default value is 'moderate'.moderate
spellcheckNoWhether to spellcheck provided query.
search_langNoSearch language preference. The 2 or more character language code for which the search results are provided.en

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv2.1.3
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed5 schema fields changedv2.0.66
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / freshness / anyOf
      Previous value: -[
-  {
-    "const": "pd",
-    "type": "string"
-  },
-  {
-    "const": "pw",
-    "type": "string"
-  },
-  {
-    "const": "pm",
-    "type": "string"
-  },
-  {
-    "const": "py",
-    "type": "string"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "enum": [
+      "pd",
+      "pw",
+      "pm",
+      "py"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}to\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  }
+]
    • addedInput schema / properties / safesearch / anyOf
      Added value: +[
+  {
+    "const": "off",
+    "type": "string"
+  },
+  {
+    "const": "moderate",
+    "type": "string"
+  },
+  {
+    "const": "strict",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / safesearch / enum
      Removed value: -[
-  "off",
-  "moderate",
-  "strict"
-]
    • removedInput schema / properties / safesearch / type
      Removed value: -"string"
  3. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations provide only openWorldHint=true, which is minimal. The description mentions it 'returns structured video results with metadata' and lists the return fields, but doesn't disclose potential behaviors like pagination limits (offset max 9 is in schema, not description), rate limits, or any error conditions. For a read-only search tool, the safety profile is implied but not explicitly stated. This is adequate but could be richer.

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?

The description is efficient: a one-sentence function summary, a 'When to use' bullet list, and a one-line return format summary. It is front-loaded with the core purpose and key use cases. Each bullet adds value without redundancy. Slightly more than necessary but well-structured.

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?

The tool has 9 parameters but only 1 required (query). The schema provides exhaustive descriptions for every parameter, and the description covers the purpose and return format. Since there is no output schema, the description's note about 'JSON list of video-related results with title, url, description, duration, and thumbnail_url' compensates for missing output schema. Combined complexity is high, but the description plus schema cover everything an agent needs to call it correctly. Missing: explicit statement that it's read-only, but openWorldHint=true implies it's a safe world state. Overall complete.

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 all 9 parameters are already documented in the schema. The description adds no additional parameter semantics beyond what the schema provides. Baseline 3 is correct since the schema does the heavy lifting; no extra value from the description.

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?

The description states a specific verb ('Searches for videos'), the resource ('Brave's Video Search API'), and clearly differentiates from siblings by mentioning video-specific output fields (title, url, duration, thumbnail_url). It is immediately clear this is distinct from web, image, news, and local search tools.

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

Usage Guidelines4/5

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

The description includes a 'When to use' section that lists concrete conditions: 'need to find videos related to a specific topic... discovering video content, getting video metadata, or finding videos from specific creators/publishers'. It doesn't explicitly state when NOT to use it or name alternatives, but the context is clear and sufficient for an agent to select it appropriately among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brave/brave-search-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server