Skip to main content
Glama
Sign In
boss-agent-cli

boss-agent-cli

by can4hou6joeng4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

boss_search

Search BOSS Zhipin job listings by keyword and filter by city, salary, experience, education, and welfare to find roles matching your criteria.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
cityNo城市名称（如 北京、广州）
pageNo页码
sortNo排序方式relevance
queryYes搜索关键词（如 Golang、Python 后端）
activeNo只保留 HR 活跃度不低于该档的职位；online 只看列表、请求量与普通搜索相同，其余档位列表看不出时会逐个查详情（更慢、风控风险更高），活跃度未知的职位会被排除并写进 hints.active_filter
salaryNo薪资范围（如 20-50K）
welfareNo福利筛选，逗号分隔 AND 逻辑（如 双休,五险一金）
educationNo学历要求（如 本科）
experienceNo经验要求（如 3-5年）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • addedInput schema / properties / active
      Added value: +{
+  "description": "只保留 HR 活跃度不低于该档的职位；online 只看列表、请求量与普通搜索相同，其余档位列表看不出时会逐个查详情（更慢、风控风险更高），活跃度未知的职位会被排除并写进 hints.active_filter",
+  "enum": [
+    "online",
+    "today",
+    "3d",
+    "week",
+    "2w",
+    "month",
+    "half-year"
+  ],
+  "type": "string"
+}
  2. Addedv1.19.1
  3. Removedv1.18.0
  4. Addedv1.17.0
  5. Removedv1.16.0
  6. Changed1 schema field changedv1.14.0
    • addedInput schema / properties / sort
      Added value: +{
+  "default": "relevance",
+  "description": "排序方式",
+  "enum": [
+    "relevance",
+    "score"
+  ],
+  "type": "string"
+}
  7. First observedv1.11.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose the non-obvious role/platform constraint that would otherwise cause failed calls. It says nothing about result shape, pagination cost, or rate-limit behavior; the notable risk disclosure for the `active` filter lives only in the schema, not the description.

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?

Two short sentences followed by a compact availability tag, with the core purpose front-loaded. Every element is relevant; only minor slack from restating the filter list that the schema already covers.

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 nine-parameter search tool with no output schema and no annotations, the description is adequate but thin: it does not tell the agent what a result set looks like, how paging behaves beyond the `page` param, or how expensive the detail-fetching filters are. The critical cost/risk caveat only exists in the schema.

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 all nine parameters including the tricky `active` tiers and the AND-semantics of `welfare`. The description merely enumerates the same filter dimensions, adding no format or syntax detail beyond what is structured.

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 gives a specific verb and resource ('搜索 BOSS 直聘职位列表') plus the filter dimensions, so it is clearly distinguishable from siblings like boss_detail, boss_recommend, or boss_greet. It does not explicitly name those alternatives, but the purpose is unambiguous without opening the schema.

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 bracketed availability tag ('roles=candidate; candidate_platforms=zhipin; recruiter_platforms=-') does tell an agent when the tool is callable and when it is not, which is useful gating. However, there is no guidance on when to prefer this search over boss_recommend, boss_cities, or boss_preset_* for discovery, so routing between siblings is left to inference.

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