Skip to main content
Glama
Sign In

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.

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": "images"
  }
}

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
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
    • 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"
+}
  3. 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"
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a page holds up to 100 images, page 2 begins at result 101, and each page costs 1 credit — cost and pagination semantics an agent cannot get from the annotations.

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 clauses with zero filler; the core purpose and returned fields are front-loaded, and pagination and cost follow. Every sentence earns its place.

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?

With 11 parameters and no output schema, the description usefully enumerates the returned fields and explains pagination and cost. It omits any mention of the engine fallback or domain/date filtering behavior, which are the more complex parts of the surface, so it is strong but not fully complete.

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%, so the baseline is 3, but the description adds real meaning to the `page` parameter by explaining the offset mapping ('page 2 starts at 101'), which resolves the ambiguity between page numbering and result offsets given `num` maxes at 100. It still says nothing about engine, date, or domain filters, leaving those entirely to the schema.

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 Images') and even names the returned fields (image URL, size, title, source page). It does not explicitly differentiate itself from close siblings like search, videos, or news, so it stops short of a 5.

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 context is implied by the tool name and the pagination/credit notes, but there is no statement of when to choose this over search or videos, nor any exclusion or prerequisite. The agent must infer the choice from the 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