theprotocol.it

View saved version →

---
name: theprotocol-job-search
description: Searches and displays IT job offers from theprotocol.it using the the:protocol MCP server (search_job_offers, get_job_offer_details, get_dictionary_elements). Use this skill only when the user wants to find, browse or look up job offers for IT or technology roles (software development, DevOps, QA, data, AI/ML, security, IT support and similar) — e.g. "znajdź oferty dla senior Java developera w Krakowie", "szukam pracy zdalnej z Pythonem", "oferty DevOps w Krakowie", "find remote React jobs over 20k" — even if theprotocol.it is not mentioned by name, and when the user asks about details, requirements, salary or work mode of an offer returned by this skill. Do not use it for jobs outside IT (e.g. cook, driver, nurse, retail, warehouse or accounting roles), for job requests that name no IT role, technology or IT specialization, for writing CVs or cover letters, or for general career advice without a request for offers.
---

# the:protocol job search

Help the user find IT job offers on theprotocol.it and look at their details. The MCP server has three tools:

| Tool | Purpose |
|---|---|
| `search_job_offers` | Filtered, paginated search (max 50 per page). Returns `totalCount` plus offers with `offerId`, `groupId`, `url`, title, company, locations, work modes, contracts with salary, technologies. |
| `get_job_offer_details` | Full offer by `groupId`: responsibilities, requirements (expected/optional), technologies, benefits, recruitment stages, project description, publication and expiry dates. |
| `get_dictionary_elements` | Codes for filters: ContractType, PositionLevel, WorkSchedule, TimeUnit, Currency, SalaryKind, WorkMode, ItCompetence, ItSpecialization, Region, ModelOfPayment. |

## Scope: IT roles only

theprotocol.it lists only IT and technology jobs. Call the tools only when the request clearly concerns an IT role, a technology (e.g. Java, React, SQL, AWS) or an IT specialization (backend, frontend, DevOps, QA, data, AI/ML, security, IT support…).

- **Non-IT jobs** (e.g. "oferty pracy dla kucharza w Gdańsku", "praca jako kierowca", "nurse jobs"): do not call any tool. Say briefly that theprotocol.it covers IT jobs only.
- **No IT role or technology given** (e.g. "znajdź mi pracę w Warszawie", "find job offers"): do not search yet. Ask in one sentence which IT role or technology the user is interested in.

## How results are shown

The server renders its own interactive UI (MCP Apps widget) in the user's app for search results and offer details. You only receive the JSON; the user sees nicely formatted cards. So:

- **Do not re-list the offers in text** (no tables, no bullet list of titles/salaries). Repeating what the widget already shows is noise.
- Under the widget, write a short comment (2–4 sentences): how many offers matched in total (`totalCount`), which filters you applied (in plain words), and one useful next step — narrow down (seniority, city, salary, contract), show the next page, or open details of a promising offer.
- Refer to individual offers by title + company when useful ("the Scalo offer looks closest to what you described"), but don't duplicate their data.
- If the user asks a concrete question the widget doesn't answer directly (e.g. "which of these are B2B above 150 zł/h?", "does this offer require Kubernetes?"), answer it from the JSON — briefly and only with data actually present in the response.

Reply in the language the user writes in. Offer content is mostly Polish; translate/summarise when the user writes in another language.

## Searching

1. **Map the request to filters.** Most filters take dictionary codes, not free text. Call `get_dictionary_elements` for that dictionary.
   - Technology, role or free text → `keywords` (matches title, technology, location and company name — so results are broad; e.g. "Python" also returns analyst or PostgreSQL roles mentioning it).
   - City → `cities` (plain names, e.g. `"Warszawa"`, `"Kraków"`). Voivodeship 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.