Skip to main content
Glama
lemonskiller

boss-mcp-job-hunting

by lemonskiller

search_boss_jobs

Search and filter Boss Zhipin job postings by keyword, city, and recency. Keep only jobs published within a specified number of days.

Instructions

Search Boss Zhipin jobs by keyword and keep postings from recent days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name. Common values include 全国、北京、上海、深圳、杭州.全国
daysNoKeep jobs whose visible publish date is within this many days.
pagesNoNumber of search result pages to inspect.
keywordYesTarget role, for example "AI解决方案岗".
headlessNoRun browser headless. Set false when login or verification is needed.
city_codeNoOptional Boss city code. If provided, it overrides city.
extra_keywordsNoExtra terms that should be considered matching signals.
require_publish_dateNoDrop cards without a visible publish date when true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description must carry full burden. It only mentions filtering by recency but omits important behaviors like browser automation, login requirements, or pagination.

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?

Extremely concise single sentence, front-loaded with the verb. Every word is relevant and earns its place.

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

Completeness2/5

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

With 8 parameters and an output schema, a one-sentence description is insufficient; it omits details about city, pages, headless mode, and other important parameters.

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 baseline is 3. Description adds no extra meaning beyond the existing schema descriptions for parameters like keyword and days.

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 uses a specific verb ('Search'), identifies the resource ('Boss Zhipin jobs'), and adds scope ('keep postings from recent days'), differentiating it from sibling login-related tools.

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 on when to use this tool versus alternatives; no prerequisites or context for using with login tools are mentioned.

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/lemonskiller/boss-mcp-job-hunting'

If you have feedback or need assistance with the MCP directory API, please join our Discord server