Skip to main content
Glama

video_search

Read-only

Find videos from YouTube and Bilibili by entering a search query, with filters for platform, recency, and result count.

Instructions

Search for videos on YouTube and Bilibili.

Args: query: Search query. platforms: Video platforms to search. Default: ["youtube", "bilibili"]. max_results: Max results per platform. freshness: Time filter. format: "markdown" or "json".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
platformsNo
max_resultsNo
freshnessNo
formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Description adds that it searches multiple platforms and returns in markdown or json. Annotations (readOnlyHint=true) already cover safety, but no mention of pagination or external API behavior.

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?

Short, front-loaded description with a clear args list, no wasted words.

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?

Input parameters well-covered; output schema exists so lack of output details is acceptable. Could briefly mention result fields, but not necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage, the description explains each parameter clearly: query, platforms, max_results, freshness, format, compensating fully for missing schema descriptions.

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?

Clearly states 'Search for videos on YouTube and Bilibili' with specific verb and resource, distinguishing from sibling tools like 'image_search' and 'search'.

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?

No explicit guidance on when to use vs alternatives; implicitly for video searches but lacks when-not-to-use or exclusion criteria.

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/duguobao812718-wq/scout'

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