Skip to main content
Glama
a7512cs

mcp-server-104

by a7512cs

搜尋 104 職缺

search_jobs

Search Taiwan 104 job bank listings by keyword with filters for location, salary, experience, remote, and job type. Returns title, company, salary, skills, and URL.

Instructions

依關鍵字與篩選條件搜尋台灣 104 人力銀行的即時職缺,回傳職稱、公司、地區、薪資、需求技能與職缺網址。支援地區、薪資下限、職類、遠端、全/兼職、年資篩選,以及分頁。若 area 同名多處(如「信義區」有台北市與基隆市兩個),不會直接搜尋,改回傳 ambiguousArea 候選清單 —— 此時請向使用者確認是哪一個,再用完整名稱(如「台北市信義區」)重新搜尋。limit 只數一般職缺:廣告位(featured=true)另計、不佔名額。要完整翻頁請用 limit=20(上游每頁固定 20 筆一般職缺);跨頁彙整時用 jobId 去重(最新排序下新缺插入會使分頁窗口飄移)。keyword 適合職務/技能詞;輸入公司名稱時 104 不執行搜尋,本工具會回 companyKeyword 提示 —— 此時請改用 find_company 找到公司,再用 get_company_jobs 取得該公司職缺。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo工作地區名稱,例如 '台北市'、'新竹'(會解析成 104 官方地區代碼查詢)
pageNo第幾頁(每頁 20 筆),預設 1。想看更多職缺就往後翻頁
sortNo排序:newest 最新更新在前(找新開職缺/掃描擴編用,建議搭配 excludeFeatured=true,否則廣告位仍會無視排序卡在最前面)/ salary 待遇由高到低。不給則用 104 預設的相關性排序
limitNo一般職缺的回傳筆數上限,最多 20,預設 5。廣告位(featured=true)另計、不佔名額;要完整翻頁請用 20
remoteNo遠端工作:full 完全遠端 / partial 部分遠端 / any 兩者皆可
jobTypeNo工作性質:fulltime 全職 / parttime 兼職
keywordYes職務關鍵字,例如 'Rust 工程師'
salaryMinNo月薪下限(新台幣),例如 60000。薪資明確低於此值的濾掉;面議預設保留
experienceNo需求年資級距:under-1y(1年以下)/1-3y/3-5y/5-10y/over-10y(10年以上)
jobCategoryNo職務類別名稱,例如 '軟體工程師'、'行銷企劃'(會解析成 104 官方職類代碼查詢)
excludeFeaturedNo排除 104 付費推廣/廣告職缺(結果中 featured=true 的),預設 false。這些會被 104 硬塞在最前面、常不符合搜尋條件;想只看自然結果時設 true
excludeNegotiableNo排除「面議」(沒寫薪資)的職缺,預設 false。想只看有明確薪資時設 true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and fully delivers. It discloses non-obvious behaviors: featured ads are excluded from limit and ignore sort order, ambiguous area returns an ambiguousArea candidate list instead of searching, company keywords produce a companyKeyword hint, and newest-sort pagination windows drift and require jobId dedup. This goes well beyond the minimum.

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 long but every sentence earns its place for a 12-parameter tool with no annotations. It is front-loaded with the core purpose, then progressively covers edge cases, pagination, and sibling tool routing. The structure is logical and dense without redundancy.

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

Completeness5/5

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

Given the tool's complexity — 12 parameters, no output schema, no annotations — the description is remarkably complete. It covers return contents, filter semantics, ambiguous routing, ad behavior, pagination and dedup, and company-name fallbacks. An agent has enough information to invoke this tool correctly in nearly all scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, which sets a baseline of 3, but the description adds substantial meaning beyond the schema: limit only counts regular jobs while featured ads are separate, salaryMin preserves '面議' by default, sort=newest is best paired with excludeFeatured=true, and keyword is for job titles/skills only — not company names. Each parameter's real-world behavior is clarified.

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 opens with a specific verb + resource: search real-time 104 job bank openings by keyword and filters, and lists the returned fields (title, company, region, salary, skills, URL). It also distinguishes itself from siblings by explicitly routing company-name queries to find_company and get_company_jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: use find_company then get_company_jobs when the keyword is a company name, and instructs the agent to ask the user for clarification when area is ambiguous. It also provides pagination strategy (limit=20 for full pages, jobId for de-duplication) and suggests excludeFeatured=true for newest sort.

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