Deactivate board publication for multiple jobs in one request. Use for bulk depublishing workflows.
| Name | Required | Description | Default |
|---|---|---|---|
| jobs | Yes | Array of job IDs to depublish | |
| boards | No | Array of board identifiers to deactivate (e.g. ['indeed', 'linkedin']) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that it 'deactivates' publication, but does not detail side effects, prerequisites, or whether deactivation is reversible.
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?
The description consists of two short sentences, front-loading the action and purpose. Every word adds value, with no redundancy.
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?
For a batch operation with 2 parameters and no output schema, the description covers purpose and usage adequately. It does not explain return values, but that is not required given the lack of output schema.
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 coverage is 100% with adequate descriptions for both parameters. The tool description adds no additional semantic information beyond what is in the schema, so baseline score of 3 applies.
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?
The description clearly states the action ('Deactivate board publication') and the resource ('multiple jobs'). It distinguishes from sibling tools like hires_batch_publish_to_boards, which does the opposite. The phrase 'Use for bulk depublishing workflows' further clarifies scope.
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?
The description specifies the use case ('bulk depublishing workflows') but does not explicitly mention alternatives for single-job removal (e.g., hires_remove_from_job_board) or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
