boss_shortlist_add
Add a job to your shortlist using its security and job IDs for organized candidate tracking.
Instructions
将职位加入候选池
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| security_id | Yes | 职位安全 ID | |
| job_id | Yes | 加密职位 ID |
Add a job to your shortlist using its security and job IDs for organized candidate tracking.
将职位加入候选池
| Name | Required | Description | Default |
|---|---|---|---|
| security_id | Yes | 职位安全 ID | |
| job_id | Yes | 加密职位 ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states the basic action. Lacks disclosure of side effects, idempotency, rate limits, or return behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is a single sentence, highly concise. No wasted words, appropriate for a simple operation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity and 100% schema coverage, the description is functionally adequate but lacks information about outcomes or error handling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description explicitly states action ('add') and resource ('job to candidate pool'). Clearly distinguishes from sibling tools like boss_shortlist_list and boss_shortlist_remove.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives. Among siblings, there are add/remove/list for shortlist, but no context or conditional instructions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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