Skip to main content
Glama

google_videos

Retrieve Google video search results with localized and filtered queries. Supports pagination, country/language settings, and time filters.

Instructions

Retrieves Google video search results with geographic localization, language preferences, and advanced filtering. Costs 5 API credits per request. [Credits: 5 API credits per request] Notes: Pagination via page (0-indexed). Returns: { video_results: [{title, thumbnail, link, displayed_link, time, rank}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lrNoLimit search to one or multiple languages, formatted lang_{language code}, e.g. lang_us.
tbsNoAdvanced parameter ('to be searched') to filter search results.
htmlNoReturn the response as raw HTML instead of JSON. (default: false)
nfprNoSet 1 to exclude auto-corrected/misspelled-query results, 0 to include them. (default: 0)
pageNoPage number of Google search results. 0 = first page, 1 = second page, etc. (default: 0)
safeNoAdult content filter. Allowed values: active, off. (default: off)
uuleNoEncoded geographic location/locale to tailor results, e.g. w+CAIQIFJlbGF5IFN0YXRlcw==.
queryYesGoogle query. Example: query=shoes
domainNoGoogle domain for local results, e.g. google.co.in for India, google.co.uk for the UK. (default: google.com)
countryNoISO country code for the Google search results. (default: us)
languageNoLanguage of the results, e.g. en, es, fr, de. (default: en)
result_timeNoCompanion to the tbs parameter for time-range filtering (e.g. language, country, file type, etc). Example value: qdr:d.
Behavior3/5

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

No annotations are provided. The description adds credit cost, pagination behavior, and return format, but does not disclose rate limits, authentication requirements, or any destructive actions. It covers basic behavioral aspects but lacks depth.

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 three sentences long with no wasted words. The first sentence states the core purpose, followed by credits and a pagination note, and finally the return format. It is efficiently structured and front-loaded.

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 lack of output schema, the description provides a sample return structure and explains pagination. It covers essential operational details for a search tool, though it could include error scenarios or result limits.

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 minimal extra meaning: notes that 'page' is 0-indexed and provides an example of the return structure. However, it does not elaborate on parameter interdependencies or usage recommendations.

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 retrieves Google video search results with specific features like geographic localization and language preferences. It uses a specific verb ('Retrieves') and resource ('Google video search results'), distinguishing it from siblings like google_images or google_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?

The description mentions pagination and credits cost but does not explicitly state when to use this tool over alternatives. No guidance on when not to use it or which sibling tools are better for other search types.

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/alessandrobenigni/ScrapingDog-MCP'

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