Skip to main content
Glama
dodou

brave-search-mcp

by dodou

brave_video_search

brave_video_search

Search for videos by topic or keyword and retrieve structured results with metadata including title, URL, description, duration, and thumbnail. Ideal for finding video content or metadata from specific creators or publishers.

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
queryYesThe user's search query. Query cannot be empty. Limited to 400 characters and 50 words.
countryNoSearch query country, where the results come from. The country string is limited to 2 character country codes of supported countries.US
search_langNoSearch language preference. The 2 or more character language code for which the search results are provided.en
ui_langNoUser interface language preferred in response. Usually of the format <language_code>-<country_code>. For more, see RFC 9110.en-US
countNoNumber of results (1-50, default 20). Combine this parameter with `offset` to paginate search results.
offsetNoPagination offset (max 9, default 0). Combine this parameter with `count` to paginate search results.
spellcheckNoWhether to spellcheck provided query.
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
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').
Behavior3/5

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

The description implies a read-only search operation, which aligns with the openWorldHint annotation. However, it does not disclose any potential side effects, authentication needs, or error behaviors beyond what annotations provide. With no destructiveHint or readOnlyHint, a bit more context would be beneficial.

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 with only three sentences plus bullet points. It is front-loaded with purpose and usage, and every sentence adds unique value. No unnecessary repetition.

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?

Given the 9 parameters and no output schema, the description covers the return format (title, url, etc.) but omits details on pagination or result limitation. Overall it is reasonably complete for a search tool with well-documented schema.

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 schema already documents all parameters. The description only mentions return fields, not adding meaning beyond what the schema provides. The 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 the tool searches for videos using Brave's Video Search API, with a specific verb and resource. It distinguishes from sibling tools like brave_image_search and brave_web_search by 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 'When to use' section provides clear contexts for video searches, such as discovering video content or finding specific creators. It does not explicitly state when not to use or name alternatives, but the context is clear enough for an AI agent.

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

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