Skip to main content
Glama
a7512cs

mcp-server-104

by a7512cs

取得 104 職缺的應徵者分析

get_apply_analysis

取得單筆 104 職缺的應徵者分析:兩週內不重複應徵人數(total —— 職缺頁與 search_jobs 的 applyRange 只有區間)與應徵者組成:學歷、年齡、年資、語言(含程度)、科系、技能、證照(每項有 count 人數與 percent 比例)。104 已不提供性別。total 的來源看 totalBasis:api=104 直接給的;inferred=104 自 2026-10…

Instructions

取得單筆 104 職缺的應徵者分析:兩週內不重複應徵人數(total —— 職缺頁與 search_jobs 的 applyRange 只有區間)與應徵者組成:學歷、年齡、年資、語言(含程度)、科系、技能、證照(每項有 count 人數與 percent 比例)。104 已不提供性別。total 的來源看 totalBasis:api=104 直接給的;inferred=104 自 2026-10 起不再直接給人數,改由它的比例反推、並用人數區間驗證過;unknown=推不出來,total 與 count 為 null,只引用 percent,不要自己估人數。totalCandidates 多於一個(多半是「30 人以上」)時 total 取最小值 —— 只有在每一項人數剛好有公因數時才會是倍數,回答時可註明「推算值」。⚠️ 只在使用者明確要求「這個職缺的應徵者/應徵人數/競爭狀況」時才呼叫;搜尋職缺、看職缺詳情、列公司職缺時不要主動呼叫,也不要為了順便比較競爭度而對多筆職缺批次呼叫。科系/技能/證照只回前 10 名,count 加總不等於 total。資料由 104 每日更新一次(updateTime)。傳入 search_jobs / get_company_jobs 回傳的 url 或 jobId。

Input Schema

NameRequiredDescriptionDefault
jobUrlOrIdYes職缺網址或代碼,例如 'https://www.104.com.tw/job/7bsyk' 或 '7bsyk'(跟 get_job_detail 相同)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and delivers rich context: data update frequency (daily), totalBasis semantics (api/inferred/unknown), how total is derived when totalCandidates > 1, that some categories are top-10 only and sums may not equal total, and that gender is no longer provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information is front-loaded with the core purpose, then nuances in separate sentences. It is dense but every sentence adds operational value; however, the length (especially the totalBasis explanation) could be slightly tightened for quicker scanning.

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 a single parameter with full schema coverage and no output schema, the description is complete: it explains how to obtain the input, what the response contains, how to interpret totals and percentages, and critical caveats about data recency and partial listings.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents the single parameter. The description adds that the input should be the url or jobId returned by search_jobs/get_company_jobs, which reinforces correct usage beyond the schema example.

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 states a specific verb and resource ('取得單筆 104 職缺的應徵者分析') and immediately clarifies that it is for a single job's applicant analysis, distinguishing it from search_jobs, get_job_detail, and get_company_jobs by scope and data type.

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?

It provides explicit when-to-use and when-not-to-use guidance: only when the user explicitly asks about applicants/application counts/competition for a specific job, and it warns against calling it proactively during job searches, detail views, or company job listings, or batching for comparison.

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