Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Google Shopping

shopping
Read-onlyIdempotent

Search products with prices and merchants. 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": "shopping"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
pageNo
countryNoCountry code, e.g. us, de, ru
languageNoLanguage code, e.g. en, ru (Russian). Does not change country
locationNoCity-level location, e.g. "Austin, Texas, United States"

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. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that with the credit cost. However, it says nothing about result volume, how country/language affect results, or the 10-page cap on results.

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?

Two telegraphic fragments, front-loaded with the core purpose and the cost last. Nothing is wasted, though the fragment style borders on under-specification.

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?

With five parameters, no output schema and a simple read-only annotation set, this is nearly adequate: the description says results carry prices and merchants. It falls short on pagination bounds, result-count expectations, and how location/country/language shape results — details an agent would need to call it well.

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 80%, so q, country, language and location are already documented in the schema. The description adds no parameter meaning at all, leaving 'page' (which lacks a schema description) and the interaction between country and language undocumented outside the schema's own hints.

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 gives a specific verb and resource ("Search products") plus the content returned (prices and merchants), which is clearer than the bare name 'shopping'. It does not explicitly contrast with siblings like search, images, or news, so an agent must infer that this is the product-oriented sibling.

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 only guidance is the cost line "1 credit"; there is no statement of when to choose shopping over the generic search tool or which queries suit it. Usage is implied by the word 'products' but no alternatives or exclusions are named.

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