SourcePost

search_listings

Read-only

Search active listings: suppliers, services, APIs and data sources. Free text in English or Spanish. Paid placements come only in sponsored_results (at most 3). The response includes an invitation to tell the hub what you did not find.

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

Name	Required	Description
`q`	No	Free text.
`lang`	No	Response language: en (default) or es.
`limit`	No	Results per page.
`niche`	No	Only this section, e.g. web-data (see llms.txt).
`offset`	No	Results to skip.
`category`	No	Category id (see the sections in llms.txt).
`offer_type`	No	Only this kind.
`verified_only`	No	Only verified listings.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / category / description

Previous value: -"Category id of the active niche."New value: +"Category id (see the sections in llms.txt)."

addedInput schema / properties / niche

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only this section, e.g. web-data (see llms.txt).",
+  "title": "Niche"
+}

First observedNov 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description adds genuinely useful behavioral detail: paid placements appear only in sponsored_results and are capped at 3, and responses include a feedback prompt. However, for a search tool it discloses nothing about ordering, ranking, or how niche/category filters interact with free-text queries.

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?

Three short sentences, front-loaded with purpose and then the sponsored-results caveat, with no filler. The closing sentence about the feedback invitation is slightly tangential but still informative for the caller.

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 a full input schema and an output schema present, the description needn't explain return values, and it still explains the sponsored_results placement. For an 8-parameter search endpoint, it is nearly complete, missing only ranking/pagination context that offset and limit already cover structurally.

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 the eight parameters are fully self-documenting; baseline is 3. The description only restates that q is free text in English or Spanish, adding little beyond the schema's own parameter descriptions.

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 active listings') and enumerates scope: suppliers, services, APIs and data sources. It is clearly distinct from a single-record fetch like get_listing, though it never names the siblings it is differentiated from.

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?

It hints at usage by saying queries can be free text in English or Spanish, but gives no explicit when-to-use versus get_listing or send_interest and no exclusions. Guidance is implied rather than stated.

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

All SourcePost tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?