Skip to main content
Glama
liepin-workbuddy-mcp

liepin-workbuddy-mcp

by 1Bruce-eng

liepin_search_jobs

Search job listings through the official Liepin CLI with city, job title, salary, education, experience, company, and pagination filters; returns raw JSON for downstream parsing.

Instructions

使用猎聘官方 CLI 搜索职位。薪资和筛选值按猎聘 CLI 支持格式原样传入;page 从 0 开始。

返回官方 CLI 原始 JSON,不假设字段结构。调用前应确认目标城市、岗位和薪资条件已明确。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "liepin_search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
addressNo
job_nameNo
edu_levelNo
salary_capNo
comp_natureNo
salary_kindNo
company_nameNo
salary_floorNo
work_experienceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two meaningful behaviors: page is 0-indexed and the return is raw CLI JSON with no assumed field structure. It does not mention auth requirements, rate limits, total result count, or how many items a page returns, which matters for a scraping-style search.

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?

Short and front-loaded: what the tool does first, then format caveats, then return behavior, then a precondition. No filler sentences. It could be slightly better organized by grouping the parameter-format notes together.

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?

Output schema exists, so return shape need not be described (and the 'raw JSON, don't assume fields' note is a helpful extra). But with 10 undescribed, enum-less, all-optional parameters, the description compensates only partially — an agent still lacks enough to fill salary and filter fields confidently.

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

Parameters2/5

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

Schema coverage is 0% and none of the 10 parameters (salary_floor, salary_cap, salary_kind, comp_nature, edu_level, work_experience, address, job_name, company_name, page) has a description or enum. The description only clarifies that filter values must be passed as raw CLI-format strings and that page is 0-based; it never explains the expected format or accepted values for salary/edu/experience filters, leaving the agent to guess.

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?

States a specific verb and resource ("搜索职位" / search jobs) and names the channel (Liepin official CLI). Siblings (get_resume, apply_job, update_job_expectation) are clearly different operations, so differentiation is implicit rather than argued. It could not be confused with anything else in the toolset.

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?

"调用前应确认目标城市、岗位和薪资条件已明确" gives a pre-call checklist, which is useful implied usage guidance. However, it never says when this tool is the right choice versus not calling it at all (e.g. no results / different query strategy), and no alternatives are named. Guidance is present but thin.

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