Skip to main content
Glama
can4hou6joeng4

boss-agent-cli

by can4hou6joeng4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

boss_search

Search BOSS Zhipin job listings by keyword and apply filters for city, salary, experience, education, and benefits to find matching positions.

Instructions

按关键词和筛选条件搜索 BOSS 直聘职位列表。支持城市、薪资、经验、学历、福利等多维度筛选。 [可用性: 可用性: roles=candidate; candidate_platforms=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年）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.1
  2. Removedv1.18.0
  3. Addedv1.17.0
  4. Removedv1.16.0
  5. Changed1 schema field changedv1.14.0
    • addedInput schema / properties / sort
      Added value: +{
+  "default": "relevance",
+  "description": "排序方式",
+  "enum": [
+    "relevance",
+    "score"
+  ],
+  "type": "string"
+}
  6. First observedv1.11.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. '搜索' implies a non-mutating read operation, and the availability tag adds useful access constraints. However, it does not disclose pagination behavior, result size, rate limits, or whether no results are returned in a specific way.

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 concise and front-loaded with the core action and resource. The duplicated '可用性: 可用性:' text introduces minor redundancy, but otherwise every phrase contributes useful information.

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?

The description covers the basic purpose, filter dimensions, and availability constraints. However, with no output schema, it does not explain the return structure, how page and sort interact, or how to follow up with detail tools like boss_detail, leaving an agent to infer these aspects.

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 explains every parameter. The description only paraphrases the filter dimensions (city, salary, experience, education, welfare) without adding meaning beyond what the schema provides, meeting the baseline.

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 states a specific verb ('搜索'), a specific resource ('BOSS 直聘职位列表'), and the supported filtering dimensions. This clearly distinguishes it from sibling tools such as boss_recommend, boss_detail, and boss_crawl_results, which serve different purposes.

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 makes the core use case clear: search jobs by keyword and filters. The availability tag adds explicit role/platform constraints (candidate only, zhilian/zhipin, no recruiter platforms), but it does not name alternatives or state when to prefer this tool over browsing or recommendation siblings.

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

Deploy Server

Other Tools