Skip to main content
Glama
104 Job Hunter MCP

104 Job Hunter MCP

by YuJunWang

job104_save_company

將指定的公司代碼加入您 104 帳號的追蹤名單中。此工具會直接執行寫入操作,需先確認已登入。

Instructions

將指定的公司代碼加入您 104 帳號的追蹤名單中。此工具會直接執行寫入操作,需先確認已登入。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companyInput": "<companyInput>"
    },
    "name": "job104_save_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyInputYes公司代碼或是公司網址。例如 '1a2x6bmutz' 或 'https://www.104.com.tw/company/1a2x6bmutz'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.5

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of disclosure. It correctly identifies the tool as a direct write operation and notes the login requirement, but it does not explain duplicate handling, idempotency, what is returned, or what happens if the company is already tracked.

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?

The description is two short sentences and front-loads the core action before the authentication prerequisite. There is little wasted text, though the second sentence could be slightly more informative for a mutation tool.

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?

For a one-parameter mutation tool with no annotations and no output schema, the description covers the basic purpose, write behavior, and login prerequisite. It is still incomplete because it omits result behavior, duplicate-save semantics, and operational caveats that matter for a write operation.

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?

Schema description coverage is 100%, and the single parameter is already documented as accepting either a company code or company URL. The description adds no parameter syntax or format details beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: adding a specified company code to the user's 104 account tracking list. It clearly distinguishes a company-tracking action from job-saving or company-detail retrieval, though it does not explicitly contrast with sibling tools such as job104_save_job.

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

Usage Guidelines3/5

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

The description gives an important prerequisite: the user must already be logged in. However, it does not state when to use this tool versus job104_search_companies or job104_get_company_detail, nor does it describe exclusions or alternatives.

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