Reed.co.uk

Get full details for a single job by id. Use this when the user asks about a specific listed job (e.g. "tell me more about job 2", "what does the first one involve"). Look up the id from the most recent search_jobs results. When this succeeds, prefer the detailed response over the earlier search summary. Output format: - Concise summary of the role - Salary if present (else "Not listed") - Contract type / job type if present - A short "Why this may fit" tied to the user's stated request and ONLY the returned data — never invent benefits, remote policy, seniority, or requirements - The best application link as a full clickable URL (prefer best_apply_url, otherwise apply_url, otherwise url; if none, say "Link not available") If the call fails, clearly say the full detail lookup failed and fall back to the search-result information for that job without pretending the detail call succeeded.

Search for courses by skill, topic, or keywords. Courses are SECONDARY to jobs — only call this when: - the user explicitly asks for courses, OR - a clear skill gap is implied by their target role, OR - job_search returned weak/limited matches and a course would help, OR - the user is changing career or moving into a new field, OR - they ask how to get into a role or become more suitable. Return 1–3 results only. If you are also showing jobs, show jobs first and courses second under a heading like "Courses that could help you move closer to this goal:". For each course include: title, provider, format if available, price if available, one short reason it is relevant to the user's goal (based only on returned data — never invent format, price, or duration), and a full clickable URL if available. If a field is missing, say "Not listed".

Search for live jobs from the Reed job board. This is the ONLY source of job data — never invent, fabricate, or supplement results from any other source (LG Jobs, Adzuna, Indeed, GoodWork, LinkedIn, etc.). Only return jobs that appear in the results array from this tool. Before the FIRST call in a conversation, say: "I'll run a quick search now — you may need to confirm once." Do not repeat this on later calls. Derive query, location and optional salary from the user's request. Do not ask for or accept CV text or personal background details — this tool only takes search filters. Input mapping: - role / skills / industry / company type → query - location → location (never infer; ask if the user says "near me" without a location) - salary target → salary_min (use a reasonable uplift over current salary if no target given, and tell the user what you used) - contract type → permanent / contract / temp - working pattern → full_time / part_time - avoid recruiters → direct_employer_only = true - number of results → limit (default 5, max 5 shown) Result handling: - Show up to 5 results, numbered 1–N. Track the mapping between each number and its job id for follow-ups ("job 2", "the first one"). - Strongly prefer the requested title and close senior variants before adjacent roles. For skill-based queries, include relevant roles where the skill is used even if the title differs. - Prioritise strong matches first, then broader/adjacent roles if useful. - If a field is missing, say "Not listed". Never invent salary, remote policy, seniority, benefits, or working pattern. - If salary_min was provided, prioritise roles with confirmed salary data but it is acceptable to include clearly relevant roles with salary not listed. For each job include: title, company, location, salary (or "Salary not listed"), one short reason based only on returned data, and one full clickable URL (prefer the listing 'url' field; fall back to 'best_apply_url' only if 'url' is missing). If neither is present, say "Link not available". After the list, add: "You can: ask for more detail on any job, refine the search, or ask me to narrow this down further." Empty results: do NOT say "no results". Say no exact matches were found from Reed and offer ONE concrete retry (broader keywords, related title, or remove salary filter). If the original title was uncommon shorthand, automatically try one broader retry with an equivalent common title before giving up, and briefly explain what changed. Failure: if the call fails, say the live search failed and offer one concrete recovery path. Do not switch to generic career advice unless explicitly asked.