Skip to main content
Glama

boss_search

Find relevant job posts on BOSS Zhipin using keyword and multi-dimensional 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年)
Install Server

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says the tool searches and supports filters, omitting result shape, pagination behavior, permissions, rate limits, or any side effects.

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 core description is short and front-loaded with the action and filter capabilities. However, the availability line contains a duplicated '可用性: 可用性:', which adds noise and slightly weakens the structure.

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 simple list-search tool, the required query and optional filters are adequately covered by the description and schema. But there is no output schema and no guidance on result format, pagination expectations, or when to prefer this tool, leaving meaningful gaps.

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 coverage is 100%, so the input schema already documents all eight parameters. The description names several filters redundantly but adds no semantic detail beyond what the schema provides.

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 action ('搜索...职位列表') and resource (BOSS直聘 job list), and names the key filter dimensions. It is clearly a query-based list search, but it does not explicitly distinguish itself from sibling tools like boss_recommend or boss_show.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as boss_recommend, boss_show, or boss_detail. The description only states what the tool does, with no selection criteria or exclusion conditions.

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

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