Skip to main content
Glama
Sign In
100Hires MCP Server

100Hires MCP Server

Official
by 100Hires
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hires_batch_remove_from_boards

Deactivate board publication for multiple jobs in one request. Streamline bulk depublishing workflows by removing jobs from selected boards.

Instructions

Deactivate board publication for multiple jobs in one request. Use for bulk depublishing workflows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobs": "<jobs>"
    },
    "name": "hires_batch_remove_from_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobsYesArray of job IDs to depublish
boardsNoArray of board identifiers to deactivate (e.g. ['indeed', 'linkedin'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior2/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 only restates the action without revealing consequences like mutating job-board associations, what happens when the optional 'boards' parameter is omitted, or whether the operation is reversible. This is a significant gap for a mutation tool.

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?

The description is two sentences, both purposeful. The first sentence states the core functionality, and the second provides usage guidance. No redundant or filler content.

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?

This is a mutation tool with no output schema and no annotations. The description does not cover what happens on partial failure, the meaning of an empty boards array, or return values. The presence of related sibling tools (e.g., batch_publish_to_boards) helps but does not make the description complete. Significant gaps remain.

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%: both 'jobs' and 'boards' have descriptive comments. The description does not add meaning beyond the schema; it just implies the endpoint's purpose. The baseline of 3 applies because the schema already documents parameters clearly.

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 clearly states the tool's action: 'Deactivate board publication for multiple jobs in one request.' This is a specific verb-resource pairing that distinguishes it from singular alternatives like hires_remove_from_job_board and the inverse bulk operation hires_batch_publish_to_boards.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use for bulk depublishing workflows,' which provides clear context for when to use the tool. However, it does not explicitly name alternatives or state when not to use it, such as for single-job depublishing.

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