Skip to main content
Glama
serper-search-mcp-server

serper-search-mcp-server

search_videos

Search Google videos by query and retrieve titles, channels, durations, and links, with filters for country, language, freshness, and safe search.

Instructions

Google Video search via Serper API. Returns titles, channels, durations, and links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesVideo search query.
countryNoISO 3166-1 alpha-2 country code (e.g. "US", "GB"). Default: "US".
ui_langNoUI language (e.g. "en-US"). Default: "en".
freshnessNoTime filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results ("today", "this week", "latest", current year); omit or "any" for timeless or historical questions. The response footer echoes the filter that was applied.
safesearchNo"off" | "moderate" | "strict". Default: "moderate".moderate
num_resultsNoResults (1–20, default 10). Note: >10 results uses 2 Serper credits.
search_langNoLanguage code (e.g. "en", "de"). Default: "en".
link_resolutionNoGoogle result links beyond the top 3 may come back as google.com/goto redirects. "auto" (default): top 3 resolved, any leftover goto links get a search_id for resolve_links. "all": also resolve every link now (free, but adds ~30 s when goto links are present). "none": fastest, links exactly as Google returns them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.0
    • changedInput schema / properties / freshness / description
      Previous value: -"Time filter: pd=day pw=week pm=month py=year."New value: +"Time filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results (\"today\", \"this week\", \"latest\", current year); omit or \"any\" for timeless or historical questions. The response footer echoes the filter that was applied."
    • changedInput schema / properties / freshness / enum
      Previous value: -[
      -  "pd",
      -  "pw",
      -  "pm",
      -  "py"
      -]New value: +[
      +  "pd",
      +  "pw",
      +  "pm",
      +  "py",
      +  "any"
      +]
  2. First observedv4.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return shape (titles, channels, durations, links), which is genuine behavioral information. It omits the credit cost of num_results > 10 and the fact that link resolution can add ~30s and hand leftover links to resolve_links — both only visible in the schema.

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?

Two short sentences, purpose first, return fields second, with zero filler or repetition. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with nuanced behavior (credit tiers, redirect resolution costs, resolve_links handoff), the description is thin, but the 100%-covered schema does the heavy lifting and it roughly documents return values in the absence of an output schema. The link-resolution and credit side effects remain undisclosed in prose.

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 every parameter including the freshness enum guidance and link_resolution modes is already documented in the schema. The description adds no parameter meaning beyond that, which is exactly the baseline 3 case.

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?

Names a specific verb and resource ("Google Video search via Serper API") and lists what comes back (titles, channels, durations, links). The word "Video" implicitly separates it from siblings like search_images, search_news and search_web, though no sibling is named explicitly.

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?

The description gives no when-to-use guidance: it never says to prefer this over search_web or search_many for video intent, and offers no exclusions or preconditions. Any routing guidance lives entirely in the schema's freshness and link_resolution parameter text, not in the description.

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