Skip to main content
Glama

Search jobs in Switzerland

search_jobs
Read-onlyIdempotent

Search open jobs in Switzerland and Liechtenstein by keywords and filters. Only jobs whose advert is still online are returned. Lehrstellen are listed only with segment apprenticeships. Returns up to 20 jobs per page, newest first for filter-only searches; keyword searches rank by relevance, favouring recent adverts and mixing companies. Use get_job for a job's full description.

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_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoA role key from list_categories; requires its category.
limitNo
queryNoKeywords matched against job title, company and description, with German word forms (e.g. "Pflegefachfrau", "Software Engineer Python"). All words must match; use OR between alternatives, "quotes" for phrases and -word to exclude. Place names match only the text; use cantons to filter by location.
cursorNonextCursor of a previous search_jobs result; the other arguments are then ignored.
cantonsNoTwo-letter canton codes (ZH, BE, VD, GE, …) or LI for Liechtenstein.
segmentNojobs (default): regular jobs and internships. apprenticeships: only Lehrstellen (Swiss vocational apprenticeships, Berufslehre). A search lists one of the two, never both.jobs
categoryNoA category key from list_categories.
workModesNo
senioritiesNo
workloadMaxNoHighest workload in percent of full time (10–100).
workloadMinNoLowest workload in percent of full time (10–100).
salaryStatedNoOnly jobs whose advert states a salary.
contractTypesNoNot for segment apprenticeships.
advertLanguagesNoLanguage the advert is written in.
excludeAgenciesNoLeave out recruitment agencies.
requiredLanguagesNoOnly jobs that require all of these languages.
publishedWithinDaysNo

Output Schema

NameRequiredDescriptionDefault
totalYesHow many open jobs match.
resultsYes
searchUrlYesThe same search on jopp.ai.
nextCursorYesPass as cursor for the next page; null at the end.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / results / items / properties / lastSeenAt
      Removed value: -{
      -  "description": "ISO date jopp last saw the advert online; a job is listed only while it is.",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "id",
      -  "url",
      -  "title",
      -  "company",
      -  "isAgency",
      -  "locations",
      -  "workload",
      -  "workMode",
      -  "contractType",
      -  "seniority",
      -  "salary",
      -  "summary",
      -  "publishedAt",
      -  "lastSeenAt"
      -]New value: +[
      +  "id",
      +  "url",
      +  "title",
      +  "company",
      +  "isAgency",
      +  "locations",
      +  "workload",
      +  "workMode",
      +  "contractType",
      +  "seniority",
      +  "salary",
      +  "summary",
      +  "publishedAt"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / contractTypes / description
      Added value: +"Not for segment apprenticeships."
    • changedInput schema / properties / contractTypes / items / enum
      Previous value: -[
      -  "permanent",
      -  "temporary",
      -  "internship",
      -  "apprenticeship",
      -  "freelance"
      -]New value: +[
      +  "permanent",
      +  "temporary",
      +  "internship",
      +  "freelance"
      +]
    • addedInput schema / properties / segment
      Added value: +{
      +  "default": "jobs",
      +  "description": "jobs (default): regular jobs and internships. apprenticeships: only Lehrstellen (Swiss vocational apprenticeships, Berufslehre). A search lists one of the two, never both.",
      +  "enum": [
      +    "jobs",
      +    "apprenticeships"
      +  ],
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedOutput schema / properties / results / items / properties / url / description
      Previous value: -"The job on getjopp.app."New value: +"The job on jopp.ai."
    • changedOutput schema / properties / searchUrl / description
      Previous value: -"The same search on getjopp.app."New value: +"The same search on jopp.ai."
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, and the description adds substantial context beyond that: only live adverts are returned, apprenticeships and regular jobs are never mixed, page size is capped at 20, filter-only searches are ordered newest-first while keyword searches are ranked by relevance with recency bias and company mixing. These are result-set behaviors an agent cannot infer from the annotations or schema.

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?

Five tight sentences with the resource, scope, inclusion rules, ordering behavior and the handoff to get_job front-loaded in that order. No filler and no repetition of the title.

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 17-parameter search tool with an output schema and rich annotations, this covers the semantics an agent most needs: segment exclusivity, pagination cap, ordering, and cursor reuse. Minor gaps remain, such as whether multiple filter families combine as AND or how enum arrays like workModes/seniorities are treated.

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 76%, so most parameters already document themselves, and several description details (role requiring its category, cursor ignoring other arguments, place names matching only text) merely restate schema text. The description adds no meaning for workModes, seniorities, workload, salaryStated or publishedWithinDays, so the 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?

The first sentence names a specific verb (search) and resource (open jobs) plus the geographic scope (Switzerland and Liechtenstein), so the tool is identifiable without opening the schema. It further scopes itself with 'Only jobs whose advert is still online' and separates itself from get_job, which returns full descriptions.

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?

It gives clear routing to get_job for a job's full description and states the Lehrstellen condition ('listed only with segment apprenticeships'). It also implies when keyword search vs filter-only search applies via the ranking note. It does not, however, say when this tool is preferable to the sibling 'search' tool or state any exclusions beyond the segment rule.

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