SynapticRelay freelance board

Search listings

search_listings

Read-only

Search active listings in any of the six languages by free text and filters. "offer" = someone provides a service; "request" = someone needs work done. Returns structured fields for comparison. Each result has match: "all_words", "some_words" (no listing had every word) or "similar_in_meaning". Results similar in meaning come only when no listing has every word, instead of any-word matches (understood.similar_in_meaning counts them): they are about the same thing but are not word matches, so tell your person that.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No
`sort`	No	relevance (default with a query), new, price_asc, price_desc (prices compared across currencies)
`limit`	No
`query`	No	Free text in any language, e.g. "logo designer" or "перевод договора". A budget in the text ("under 500 EUR") becomes a price filter unless you pass max_price.
`offset`	No
`category`	No	ai-automation: AI agents, chatbots on language models, MCP servers, n8n/Make/Zapier automations; development: websites, apps and other software; it-support: fixing and setting up computers, servers and accounts.
`currency`	No	Currency of max_price/min_price; listings in other currencies are compared at the day’s exchange rate
`language`	No	Language for texts in the response (default: your person’s language). It does not pick authors who work in it: use work_language for that
`lang_pair`	No	Translation direction "from>to", e.g. "es>de" (Spanish into German)
`max_price`	No	Upper bound for the listed price or budget, compared as it is: an hourly price per hour, a "from" price as its minimum (read price_type)
`min_price`	No	Lower bound, e.g. the smallest budget worth taking; compared as it is: an hourly price per hour, a "from" price as its minimum (read price_type)
`work_language`	No	ISO code of a language the author works in, e.g. "en", "es" (language below only translates the texts)
`max_delivery_days`	No	Done or due within this many days: offers whose delivery_days is at most this, requests whose needed_by is no later than this many days from today. Listings that state no term (hourly offers) stay in the results: read delivery_days and needed_by

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

addedInput schema / properties / max_delivery_days

Added value: +{
+  "description": "Done or due within this many days: offers whose delivery_days is at most this, requests whose needed_by is no later than this many days from today. Listings that state no term (hourly offers) stay in the results: read delivery_days and needed_by",
+  "maximum": 365,
+  "minimum": 1,
+  "type": "integer"
+}

First observedOct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

With readOnlyHint=true and openWorldHint=false already covering the safety profile, the description adds real behavioral detail beyond the annotations: it explains the match field values and the non-obvious rule that similar_in_meaning results only appear when no listing matches every word. It even instructs the agent to relay that caveat to the user, which is meaningful invocation-time behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and kind semantics are front-loaded and efficient, but the match-type explanation is a dense, hard-to-parse run-on ('Results similar in meaning come only when no listing has every word, instead of any-word matches (understood.similar_in_meaning counts them)...'). It conveys necessary information but the structure is muddled.

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 a 13-parameter tool with no output schema, the description compensates by explaining the shape of results (match values) and the currency/cross-field caveats are handled in the schema itself. It is complete enough to invoke correctly, with only minor gaps around result set and pagination behavior.

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 77% (below the 80% baseline), so the description must compensate, and it does for the least-documented parameter: kind is an undocumented enum in the schema and the description defines 'offer' vs 'request' explicitly. It also ties 'six languages' to the language concept, though it adds no detail for the remaining well-documented params.

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 (search) and resource (active listings) plus the scope (six languages, free text and filters), and clarifies the meaning of the two listing kinds. An agent can distinguish this discovery tool from the id-based siblings get_listing and get_author without opening any 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 through the description of offer/request semantics and the free-text-plus-filters mode, but there is no explicit when-to-use versus when to call siblings (get_listing, get_author), and no exclusions or prerequisites are stated. Adequate context but no routing guidance.

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

All SynapticRelay freelance board tools Inspect

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

Need Help?