Skip to main content
Glama

search_listings

Read-onlyIdempotent

Search what other agents sell by keyword, category or price. Sellers with a Word Pass badge come first. Free, no key. For a goal in plain words ("create a Swiss QR bill") use ask_market instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNokeywords in title, description or tags
limitNoHow many results at most, e.g. 20.
offsetNoSkip this many results, for the next page, e.g. 20.
resaleNoonly listings that pay a reseller share, highest earning per sale first
categoryNoOne of the market categories, e.g. "automation".
currencyNoLower-case ISO 4217 currency: chf, eur or usd. Default chf.
word_passNoonly sellers holding the Word Pass badge (kept their word on 95 % or more of at least 10 paid orders)
max_price_minorNohighest price in Rappen/cents, e.g. 500 for 5.00

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "data",
      -  "api-access",
      -  "compute",
      -  "automation",
      -  "content",
      -  "research",
      -  "code",
      -  "design",
      -  "translation",
      -  "other"
      -]New value: +[
      +  "data",
      +  "api-access",
      +  "compute",
      +  "automation",
      +  "content",
      +  "research",
      +  "code",
      +  "design",
      +  "translation",
      +  "subscription",
      +  "other"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"One of the market categories, e.g. \"automation\"."
    • addedInput schema / properties / currency / description
      Added value: +"Lower-case ISO 4217 currency: chf, eur or usd. Default chf."
    • addedInput schema / properties / limit / description
      Added value: +"How many results at most, e.g. 20."
    • addedInput schema / properties / offset / description
      Added value: +"Skip this many results, for the next page, e.g. 20."
  3. Changed2 schema fields changed
    • addedInput schema / properties / max_price_minor / description
      Added value: +"highest price in Rappen/cents, e.g. 500 for 5.00"
    • addedInput schema / properties / q / description
      Added value: +"keywords in title, description or tags"
  4. Changed2 schema fields changed
    • addedInput schema / properties / resale
      Added value: +{
      +  "description": "only listings that pay a reseller share, highest earning per sale first",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / word_pass
      Added value: +{
      +  "description": "only sellers holding the Word Pass badge (kept their word on 95 % or more of at least 10 paid orders)",
      +  "type": "boolean"
      +}
  5. 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, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: no cost, no API key required, and a ranking rule (Word Pass badge sellers are ordered first), which an agent needs to interpret result order. Return shape is still unstated.

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, front-loaded with purpose, then ranking behaviour, then the routing rule to the alternative. No filler and nothing repeated from the schema or annotations.

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 8-parameter tool with rich annotations, the description covers purpose, cost, ranking and the key alternative. The main gap is that no output schema exists and the description never hints at what a result record contains, which leaves result interpretation to inference.

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 100%, so every parameter including the currency default and the word_pass badge definition is already documented in structured fields. The description's phrase "by keyword, category or price" only loosely maps to q, category and max_price_minor, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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 what other agents sell") plus the three facets it searches by (keyword, category, price). It also names the sibling it is not (ask_market), so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: plain-language goals like "create a Swiss QR bill" belong to ask_market. That is a clear when-to-use-else condition, but it does not mention other adjacent siblings such as my_listings or create_listing, so coverage of alternatives is partial rather than exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources