Skip to main content
Glama

boss_search

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

Instructions

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

Input Schema

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

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

No annotations provided, and the description lacks behavioral details like pagination behavior, rate limits, or authentication. The availability note about roles/platforms is present but doesn't cover behavioral traits.

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 main description is a concise single sentence front-loaded with purpose. The bracket note adds context but has a repetition ('可用性: 可用性:') which slightly reduces clarity.

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

Completeness4/5

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

Given parameters are well-documented and no output schema exists, the description provides sufficient context for a search tool. It covers main filters and availability, though missing sorting or default page size.

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% with clear parameter descriptions. The description reiterates filter dimensions but adds no extra meaning beyond the schema.

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 clearly states it searches BOSS Zhipin job listings with keyword and filters, which is specific. However, it doesn't explicitly differentiate from sibling tools like boss_show, but the name implies search.

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?

No explicit guidance on when to use this tool vs alternatives like boss_show or boss_detail. The description only states functionality, leaving usage context unclear.

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