Skip to main content
Glama
oki602960

brave-search-mcp-server

by oki602960

brave_video_search

brave_video_search

Search for videos by keyword and retrieve structured results including 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
Behavior3/5

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

Annotations include openWorldHint=true, indicating external data access. The description adds return format details (title, url, description, etc.) but does not discuss rate limits, authentication, or potential side effects. It provides moderate transparency beyond annotations.

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?

The description is concise and well-structured, with a clear opening sentence, a bulleted usage section, and a brief return format note. No unnecessary content, and every sentence adds value.

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 description adequately covers the main purpose and return format for a video search tool with 9 parameters. However, it lacks details on error handling, pagination behavior beyond what the schema provides, and more comprehensive output structure. Still, it is mostly complete for typical use.

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?

The input schema already covers all 9 parameters with descriptions (100% coverage). The tool description does not add substantive parameter-level information beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states it searches for videos using Brave's Video Search API, specifying the resource (videos) and the action (searches). It distinguishes itself from sibling tools like brave_web_search and brave_image_search by explicitly focusing on video results.

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 provides clear context for video discovery, but does not explicitly state when not to use it or list alternatives among siblings. The context is sufficient given the distinct purpose.

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/oki602960/brave-search-mcp-server'

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