Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Google Videos

videos
Read-onlyIdempotent

Search videos. 1 credit.

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": {
      "q": "<q>"
    },
    "name": "videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
pageNo
engineNogoogle (default), auto (fall back to other engines when Google is unavailable), or brave, bing, duckduckgo; a comma-separated list also works
countryNoCountry code, e.g. us, de, ru
end_dateNoOnly results published on or before this date (YYYY-MM-DD)
languageNoLanguage code, e.g. en, ru (Russian). Does not change country
locationNoCity-level location, e.g. "Austin, Texas, United States"
start_dateNoOnly results published on or after this date (YYYY-MM-DD)
exclude_domainsNoDrop results from these sources: a domain (example.com, subdomains match), a path prefix (github.com/org) or a TLD (.gov)
include_domainsNoOnly results from these sources: a domain (example.com, subdomains match), a path prefix (github.com/org) or a TLD (.gov)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"Country code, e.g. us, de, ru. Uses shared proxy routes"New value: +"Country code, e.g. us, de, ru"
  2. Changed1 schema field changed
    • changedInput schema / properties / engine / description
      Previous value: -"google (default), auto (fall back to other engines when Google is unavailable), or brave, bing, yahoo, duckduckgo, mojeek; a comma-separated list also works"New value: +"google (default), auto (fall back to other engines when Google is unavailable), or brave, bing, duckduckgo; a comma-separated list also works"
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful cost context ('1 credit'), which is not in the annotations. However, it omits pagination behavior, result limits, and engine fallback semantics that would help an agent anticipate behavior.

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?

The description is extremely concise and front-loaded, with no filler. Both fragments carry information, though the extreme brevity leaves it under-specified for a 10-parameter search tool.

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

Completeness2/5

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

There is no output schema, so the description should explain what calling the tool returns, such as result format or pagination. It also does not explain engine fallback or credit usage beyond the single credit mention. For a 10-parameter video search tool, this is materially incomplete.

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 coverage is 90%, so the schema itself documents nearly all parameters well, including engine, country, language, location, date range, and domain filters. The description adds no parameter-specific semantics, so the baseline 3 applies.

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?

The description states a clear verb and resource: 'Search videos.' This distinguishes it from most siblings by media type, though it does not explicitly contrast with general web search or news. It is clear enough for an agent to identify the tool.

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, no exclusions, and no alternatives. It does not say whether this is preferred over general search or news for video results, leaving selection to the sibling name alone.

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

All SerpKite toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources