Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

google_videos

Search Google video vertical results by query to get titles, platforms, links, durations, and ages for research or discovery.

Instructions

Search Google video results. Returns Google video vertical results (title, platform, link, duration, age). Locale defaults to country=us and lang=en. Returns 503 when Google serves a challenge page or an unusable response.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
langNoGoogle UI language; defaults to en
pageNo1-based page number; defaults to 1
countNoResults per page; defaults to 10, clamped to 1..50
countryNoTwo-letter country code; defaults to us

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it lists the returned fields (title, platform, link, duration, age), states locale defaults, and discloses a concrete failure mode (503 on challenge/unusable responses). It omits any note on pagination limits beyond the schema, but the failure disclosure is genuinely useful behavior an agent could not infer.

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?

Three short sentences, front-loaded with the core action, then returns, then error behavior. No filler. Slightly dense in the middle sentence but every clause carries information.

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?

No output schema exists, so the description helpfully enumerates returned fields, and it flags the 503 failure path. Combined with a fully documented 5-parameter schema, an agent has what it needs to invoke correctly; only the sibling-routing gap remains.

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 q, lang, page, count, and country with defaults and clamping. The description only restates the country/lang defaults, adding no syntax, format, or constraint detail beyond the schema. Baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Google video results') and immediately narrows scope with 'Google video vertical results'. It does not distinguish itself from the many sibling video-search tools (bing_videos, brave_videos, duckduckgo_video, yahoo_search_videos, youtube_search), so an agent gets the what but not the why-this-one.

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

Usage Guidelines2/5

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

No statement of when to prefer this over the numerous other video/search tools, no prerequisites, and no exclusions. Usage is only implied by the word 'Search'. The description spends its budget on output shape and errors rather than routing guidance.

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

Deploy Server

Other Tools