Skip to main content
Glama

boss_preset_remove

Delete a named search preset to clean up saved job search filters and keep your BOSS Zhipin workflow organized.

Instructions

删除指定搜索预设 [可用性: 可用性: roles=candidate; candidate_platforms=zhilian, zhipin; recruiter_platforms=-]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes预设名称
Install Server

TDQS

A3.5/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 full burden of behavioral disclosure. It clearly indicates the destructive nature via '删除' (delete), but does not mention whether deletion is permanent, what happens if the preset name does not exist, or any side effects.

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 purpose, followed by availability info. The duplicated '可用性:' prefix is a minor formatting flaw but does not harm overall readability.

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?

For a simple one-parameter delete tool with no output schema, the description plus schema is mostly sufficient for correct invocation. A brief mention that the name can be obtained via boss_preset_list would strengthen completeness, but it is not critical.

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%, with the only parameter 'name' documented as '预设名称' (preset name). The description adds minimal additional meaning beyond referring to 'specified' preset, so it does not significantly compensate 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 the action ('删除指定搜索预设' - delete specified search preset) with a specific verb and resource. It distinguishes the tool from sibling preset tools like boss_preset_add and boss_preset_list, though it does not explicitly mention the 'name' parameter.

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 includes an explicit availability constraint (roles=candidate; platforms=zhilian, zhipin), which gives some guidance on who can use it. However, it does not mention when to prefer this tool over alternatives such as boss_preset_add or boss_preset_list, nor does it provide any exclusion conditions.

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

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