Skip to main content

Finder Jobs

Overview Discussions Admin

Search vacancies

search_vacancies

Read-onlyIdempotent

Search active job vacancies on Finder. country: ISO code (ru, by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz, uz, no, sk, bg, fi, es, pl, sg, nz, mx, co; ru = finder.work, Russia). query: job title / keywords in any language (e.g. 'бухгалтер', 'python developer'). city: city name as written locally (e.g. 'Минск', 'Алматы', 'Berlin'). Returns up to limit (≤20) newest matches with links to finder.work.

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": {
      "country": "<country>"
    },
    "name": "search_vacancies"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No	City name as written locally, e.g. 'Минск', 'Алматы', 'Berlin'. Empty = whole country
`limit`	No	Max results, 1-20 (default 10)
`query`	No	Job title or keywords in any language, e.g. 'бухгалтер', 'python developer'. Empty = newest vacancies
`country`	Yes	Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz, uz, no, sk, bg, fi, es, pl, sg, nz, mx, co

Output Schema

Name	Required	Description	Default
`count`	No
`error`	No
`total`	No
`country`	No
`results`	No
`listing_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / country / description

Previous value: -"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz, uz, no, sk, bg, fi"New value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz, uz, no, sk, bg, fi, es, pl, sg, nz, mx, co"

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / country / description

Previous value: -"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz, uz"New value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz, uz, no, sk, bg, fi"

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / country / description

Previous value: -"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz"New value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz, uz"

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / country / description

Previous value: -"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa"New value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa, gb, ie, cz"

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / country / description

Previous value: -"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at"New value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at, ar, ec, pa"

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / country / description

Previous value: -"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id"New value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id, at"

Changed5 schema fields changedOct 17, 2026

addedInput schema / properties / city / description

Added value: +"City name as written locally, e.g. 'Минск', 'Алматы', 'Berlin'. Empty = whole country"

addedInput schema / properties / country / description

Added value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id"

addedInput schema / properties / limit / description
```
Added value: +"Max results, 1-20 (default 10)"
```

addedInput schema / properties / query / description

Added value: +"Job title or keywords in any language, e.g. 'бухгалтер', 'python developer'. Empty = newest vacancies"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "VacancyCard": {
+      "properties": {
+        "city": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "City of the vacancy",
+          "title": "City"
+        },
+        "country": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Country code (search results) or country name (get_vacancy)",
+          "title": "Country"
+        },
+        "employer": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Employer name",
+          "title": "Employer"
+        },
+        "employment_type": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Employment type, e.g. full_time, part_time, contract",
+          "title": "Employment Type"
+        },
+        "excerpt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Short description excerpt (≤200 chars)",
+          "title": "Excerpt"
+        },
+        "id": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Finder vacancy id (use with get_vacancy)",
+          "title": "Id"
+        },
+        "posted_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Publication date, YYYY-MM-DD",
+          "title": "Posted At"
+        },
+        "salary": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Advertised salary range with currency, e.g. '2 000–2 500 BYN'",
+          "title": "Salary"
+        },
+        "title": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Job title",
+          "title": "Title"
+        },
+        "url": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Vacancy page on finder.work where the user can read more and apply",
+          "title": "Url"
+        },
+        "workplace": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Workplace type: onsite, remote, hybrid",
+          "title": "Workplace"
+        }
+      },
+      "title": "VacancyCard",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "count": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Count"
+    },
+    "country": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Country"
+    },
+    "error": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Error"
+    },
+    "listing_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Listing Url"
+    },
+    "results": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/VacancyCard"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Results"
+    },
+    "total": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Total"
+    }
+  },
+  "title": "SearchResult",
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A3.7/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 behavior, so the bar is lower. The description adds real value beyond them: results are limited to the newest matches, capped at 20, and include links to finder.work, plus empty-string defaults behave as 'newest' / 'whole country'.

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?

The purpose is front-loaded in the first clause, followed by compact per-parameter notes and a short return-value sentence. It is dense and list-like but every sentence carries information; no filler.

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?

An output schema exists, so return values need not be fully explained, and the description still gives the key return shape (up to limit newest matches with links). Combined with full schema coverage and annotations, an agent has what it needs to call this correctly; only cross-tool routing guidance is missing.

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 schema already documents all four parameters with the same examples. The description mostly restates them, adding only the useful nuance that 'ru' maps to finder.work specifically, which earns it the baseline rather than higher.

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 opens with a specific verb and resource ('Search active job vacancies on Finder') and constrains scope to active listings. An agent can distinguish it from get_vacancy by the plural search framing, though the description never names that sibling explicitly.

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 parameter semantics (keyword query, local city, country code), but there is no explicit statement of when to prefer this over get_vacancy or salary_stats, and no stated exclusions or prerequisites. The agent must infer the routing.

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

All Finder Jobs tools Inspect

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?