Skip to main content
Glama
afrozk

MCP Job Toolkit

by afrozk

MCP Job Toolkit

Claude 또는 MCP 호환 클라이언트 내에서 호주 채용 플랫폼 전반의 일자리를 검색하는 MCP(Model Context Protocol) 서버입니다.

플랫폼

플랫폼

참고 사항

Seek

au.seek.com의 Apollo SSR 캐시를 파싱

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에게 자연스럽게 질문하세요:

"지난 7일 동안 게시된 멜버른의 계약직 백엔드 엔지니어 역할을 찾아줘" "Seek에서 연봉 10만 달러 이상인 시드니의 정규직 데이터 분석가 일자리를 검색해줘" "지원자가 20명 미만인 브리즈번의 소프트웨어 엔지니어 역할을 보여줘"

도구: search_jobs

매개변수

매개변수

유형

기본값

설명

keyword

string

필수

직함, 역할 또는 기술 (예: "software engineer")

location

string

필수

호주 도시 또는 교외 지역 (예: "Melbourne VIC", "Sydney")

radius

number

50

검색 반경 (km 단위)

employment_type

array

all

"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

all

"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

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

Related MCP Connectors

Related MCP Servers

  • 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
  • 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
  • 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
  • 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.
    -