Skip to main content
Glama

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Google Images

images
Read-onlyIdempotent

Search Google Images: image URL, size, title and source page. A page holds up to 100 images; page 2 starts at 101. 1 credit per page.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
numNoImages to return from the page (default all, up to 100; same credit)
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. Uses shared proxy routes
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
    • addedInput schema / properties / num
      Added value: +{
+  "description": "Images to return from the page (default all, up to 100; same credit)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
  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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower; the description adds genuinely new behavioral facts — up-to-100 images per page, page 2 starting at result 101, and a cost of 1 credit per page. It stops short of describing result ordering or failure behavior when an engine is unavailable.

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?

Three short sentences: capability first, then pagination mechanics, then cost. No filler and nothing buried.

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?

For an 11-parameter read-only search tool with no output schema, the description covers what is returned, how paging works, and what it costs, with annotations and a 91%-covered schema handling safety and filters. It could mention the engine fallback and date/domain filtering as first-class capabilities rather than leaving them entirely to the schema.

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

Parameters4/5

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

Schema coverage is 91%, and the one undocumented parameter in the schema (page, which has no description) is precisely what the description explains by defining page size and the offset of page 2. That is real added meaning over the schema, though nothing is said about the filter parameters.

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?

States a specific verb and resource ("Search Google Images") and even enumerates the returned fields (image URL, size, title, source page), which lets an agent distinguish it from videos, news, shopping and search without opening the schema.

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?

Usage is implied by the name and the returned-field list, but there is no explicit statement of when to pick this over siblings such as search/videos/shopping, nor any exclusions. The pagination and credit notes are operational, not selection guidance.

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