Skip to main content
Glama
Sign In
100Hires MCP Server

100Hires MCP Server

Official
by 100Hires
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hires_remove_from_job_board

Remove a job from selected job boards by deactivating its publications. Specify the job ID and board identifiers to stop unwanted listings.

Instructions

Deactivate selected board publications for a job. Stops the job from being listed on specified boards.

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": {
      "id": "<id>"
    },
    "name": "hires_remove_from_job_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob ID (numeric) or alias
boardsNoArray of board identifiers to deactivate (e.g. ['indeed', 'linkedin'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states the main effect (stops listing on specified boards) but omits details such as reversibility, permissions, error conditions, or what happens if the boards parameter is omitted. 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 concise sentences, front-loaded with the action, and contains no redundant information. Every word contributes to clarity.

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?

Despite the tool's simplicity, the description leaves important gaps: the boards parameter is optional in the schema, but the description does not clarify what happens when it is omitted. No mention of response or side effects, and with no output schema, the description should provide more context to be fully complete.

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 for parameters is 100%, so the baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions; it merely maps 'selected board publications' to the boards parameter and 'for a job' to id, which the schema already conveys.

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 action: deactivating selected board publications for a job, which stops the job from being listed on specified boards. The verb 'deactivate' and resource 'board publications' make the purpose unambiguous and distinguish it from related tools like publish or list operations.

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 implies usage for a single job with selected boards, but it does not explicitly state when to prefer this tool over alternatives like batch removal or publishing, nor does it mention exclusions. Usage context is implied rather than explicitly guided.

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