Skip to main content
Glama
deenesjakoruzh
afrozk

MCP Job Toolkit

by afrozk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

MCP Job Toolkit

MCP-сервер (Model Context Protocol), который ищет вакансии на австралийских платформах по поиску работы из Claude или любого другого MCP-совместимого клиента.

Платформы

Платформа

Примечания

Seek

Парсит кэш Apollo SSR с au.seek.com

LinkedIn

Гостевой API вакансий, включает количество откликов, если доступно

Related MCP server: Jobs MCP Server

Установка

Предварительные требования: Node.js 18+

git clone https://github.com/afrozk/mcp-job-toolkit.git
cd mcp-job-toolkit
npm install
npm run build

Настройка Claude Desktop

Добавьте в ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) или %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "mcp-job-toolkit": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-job-toolkit/dist/index.js"]
    }
  }
}

Перезапустите Claude Desktop. Инструмент search_jobs появится автоматически.

Использование

После подключения задайте вопрос Claude в свободной форме:

"Найди вакансии контрактного backend-разработчика в Мельбурне, опубликованные за последние 7 дней" "Найди вакансии аналитика данных на полную ставку в Сиднее с зарплатой выше $100k/год на Seek" "Покажи мне вакансии инженера-программиста в Брисбене, на которые подано менее 20 заявок"

Инструмент: search_jobs

Параметры

Параметр

Тип

По умолчанию

Описание

keyword

string

обязательно

Название должности, роль или навык (например, "software engineer")

location

string

обязательно

Австралийский город или пригород (например, "Melbourne VIC", "Sydney")

radius

number

50

Радиус поиска в км

employment_type

array

все

"fulltime", "parttime", "contract", "casual"

salary_type

string

—

"hourly", "monthly", "yearly"

salary_min

number

—

Минимальная зарплата в единицах, соответствующих salary_type

salary_max

number

—

Максимальная зарплата

date_posted

string

—

"24h", "2d", "3d", "7d", "30d"

max_applications

number

—

Исключить вакансии с количеством откликов больше этого числа (где доступно)

platforms

array

все

"seek", "linkedin"

page

number

1

Номер страницы

per_page

number

10

Результатов на страницу для каждой платформы (макс. 25)

Пример вызова инструмента

{
  "keyword": "senior backend engineer",
  "location": "Melbourne VIC",
  "radius": 30,
  "employment_type": ["contract", "fulltime"],
  "salary_type": "yearly",
  "salary_min": 120000,
  "date_posted": "7d",
  "max_applications": 25,
  "platforms": ["seek", "linkedin"],
  "per_page": 10
}

Структура ответа

{
  "results": [
    {
      "platform": "seek",
      "jobs": [
        {
          "id": "seek-91878509",
          "title": "Senior Backend Engineer",
          "company": "Acme Corp",
          "location": "Melbourne VIC",
          "salary": "$140,000 – $160,000 per year",
          "description": "We are looking for...",
          "url": "https://au.seek.com/job/91878509",
          "posted_at": "2026-05-04T01:54:46.000Z",
          "applications_count": null,
          "platform": "seek"
        }
      ],
      "total": 41,
      "page": 1
    },
    {
      "platform": "linkedin",
      "jobs": [],
      "page": 1
    }
  ],
  "summary": [
    { "platform": "seek", "count": 10, "total": 41 },
    { "platform": "linkedin", "count": 8 }
  ],
  "fetched_at": "2026-05-05T00:00:00.000Z"
}

Разработка

# Run without building (uses tsx)
npm run dev

# Rebuild after changes
npm run build

# Run built server
npm start

Лицензия

MIT

Available Tools

1 tool
search_jobsA

Search for jobs across Australian job platforms: Seek and LinkedIn. Supports keyword search, location with radius, employment type, salary, date posted, and application count filters.

ParametersJSON Schema
NameRequiredDescriptionDefault
keywordYesJob title, skill, or keyword to search for (e.g. "software engineer", "data analyst")
locationYesAustralian city or suburb (e.g. "Melbourne", "Sydney CBD", "Brisbane QLD", "Perth")
radiusNoSearch radius in km from the location (default: 50)
employment_typeNoFilter by employment type. Multiple values allowed.
salary_typeNoSalary payment frequency for filtering
salary_minNoMinimum salary (in the currency unit matching salary_type, e.g. 80000 for yearly AUD)
salary_maxNoMaximum salary
date_postedNoOnly show jobs posted within this time window
max_applicationsNoOnly show jobs with fewer than this many applicants (e.g. 10, 20, 25). Not all platforms expose application count.
platformsNoWhich platforms to search (default: all)
pageNoPage number for pagination (default: 1)
per_pageNoResults per page per platform (default: 10, max: 25)

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the platforms and filters but fails to state that the operation is read-only, whether authentication is needed, or how pagination works. Important limitations (e.g., filter compatibility) are only hinted at for one filter.

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?

The description is two sentences: the first defines purpose and scope, the second lists filters. It is front-loaded with key information and contains no superfluous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high parameter count (12) and no output schema, the description covers the core function adequately but lacks details on return format, pagination behavior, or error conditions. It is minimally complete for an agent to understand basic usage.

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?

All 12 parameters have schema descriptions (100% coverage), so the description adds minimal value beyond what the schema provides. The baseline score of 3 is appropriate; the description lists filter categories but does not elaborate on individual parameters.

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 description clearly states the tool's purpose: searching for jobs on Australian platforms (Seek and LinkedIn). It lists supported filters, making it specific and informative. With no sibling tools, differentiation is unnecessary.

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?

The description implies when to use the tool (for job searches in Australia) but does not explicitly state when not to use it or provide alternatives. Since there are no siblings, the implicit guidance is sufficient.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedsearch_jobs
Deploy Server
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

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no potential for confusion with other tools. The tool's purpose is clearly defined.

Naming Consistency5/5

With a single tool, the naming follows a consistent verb_noun pattern ('search_jobs'), which is clear and predictable.

Tool Count3/5

One tool is on the low end for a 'toolkit,' feeling thin but acceptable for a focused search-only server. It borders the threshold of being too few.

Completeness2/5

The server only provides search functionality, lacking other expected operations like retrieving job details, saving jobs, or managing applications. The surface is incomplete for a comprehensive job toolkit.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • job-search-mcp

    VincenzoImp
    A
    license
    Not graded
    quality
    A
    maintenance
    MCP server that exposes job search data from multiple boards, enabling clients to query and manage job listings via natural language.
    7
    MIT

  • Jobs MCP Server

    Pragatheswar-72
    A
    license
    Not graded
    quality
    D
    maintenance
    A custom MCP server that exposes a jobs database to any MCP-compatible LLM client, allowing users to ask in plain English to search, filter, and match job openings.
    MIT

  • job-search-mcp

    OmriH-Elister
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that exposes job-search and application-management capabilities to compatible AI clients, enabling discovery of vacancies, drafting of tailored application materials, and coordinated human-approved submissions.
    MIT

  • JobScout MCP

    csarushan1729
    F
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables Claude to search live job postings, rank them against a user's skills profile, and track application statuses locally.
    -