Skip to main content
Glama

boss_search

Search BOSS Zhipin job listings by keyword and filter by city, salary, experience, education, and welfare benefits.

Instructions

按关键词和筛选条件搜索 BOSS 直聘职位列表。支持城市、薪资、经验、学历、福利等多维度筛选。

Input Schema

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

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

No annotations are provided, so the description carries full burden. It describes the tool's behavior (search and filter), but does not explicitly state that it is read-only or disclose any side effects, rate limits, or result format. Adequate but could be more explicit.

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

Conciseness5/5

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

The description is a single clear sentence in Chinese, front-loading the core purpose and listing supported filters. No unnecessary words, highly concise.

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?

Given the tool's complexity (7 parameters, no output schema), the description is functional but lacks details about return values, pagination, or result structure. It leaves the agent to infer the output format.

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 the schema already documents all parameters. The description adds context by listing supported filter dimensions, but does not provide additional semantic meaning beyond what is in the schema. Baseline 3 is appropriate.

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 Direct Recruitment job listings by keywords and filters. The name 'boss_search' aligns perfectly, and there are no similar sibling tools (e.g., no other search), so it is well-distinguished.

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

Usage Guidelines4/5

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

The description implies use for searching jobs with filters, but does not explicitly state when not to use it or mention alternatives. However, since no alternative search tool exists among siblings, this is acceptable.

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