Skip to main content
Glama

boss_search

Search BOSS Zhipin job listings by keyword with filters for city, salary, experience, education, and benefits.

Instructions

按关键词和筛选条件搜索 BOSS 直聘职位列表。支持城市、薪资、经验、学历、福利等多维度筛选。 [可用性: 可用性: roles=candidate; candidate_platforms=qiancheng, zhilian, zhipin; recruiter_platforms=-]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo城市名称(如 北京、广州)
pageNo页码
sortNo排序方式relevance
queryYes搜索关键词(如 Golang、Python 后端)
salaryNo薪资范围(如 20-50K)
welfareNo福利筛选,逗号分隔 AND 逻辑(如 双休,五险一金)
educationNo学历要求(如 本科)
experienceNo经验要求(如 3-5年)
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as authentication requirements, rate limits, side effects, or data returned. It only states basic functionality.

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 short (two sentences plus availability note) and front-loaded with the main purpose. However, the second sentence partly repeats the first, and the availability note could be more structured.

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

Completeness2/5

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

For a search tool with 8 parameters and no output schema, the description lacks crucial context: no mention of result format, pagination behavior, or how the AND logic for welfare works. Incomplete for effective use.

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%, so baseline is 3. The description lists filter types (city, salary, etc.) but adds no new information beyond what the schema already provides for each parameter.

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 searches BOSS直聘 job listings with keywords and filters, listing supported dimensions (city, salary, etc.). It distinguishes from sibling tools like boss_show or boss_detail which are for specific jobs.

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 implies usage for job searching with filters but does not explicitly state when to use this tool versus alternatives (e.g., boss_detail for specific job info). No when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/can4hou6joeng4/boss-agent-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server