Skip to main content
Glama
jobinja-employer-mcp

jobinja-employer-mcp

by saeedsepehr

Reject applicant

reject_applicant
Destructive

Mark an applicant as rejected using a reason code and optional candidate message; the candidate is notified. Set dry_run to preview the rejection form without submitting.

Instructions

Mark an applicant as rejected (نامناسب) with a reason code from list_rejection_reasons.

Jobinja notifies the candidate of the rejection; message is optional extra text sent to the candidate with it (not an internal note: use add_note for that). dry_run=true fills the rejection form without submitting it.

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": {
      "post": "<post>",
      "applicant_id": "<applicant_id>",
      "reason": "<reason>"
    },
    "name": "reject_applicant"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYes
reasonYes
dry_runNo
messageNo
page_hintNo
applicant_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, but the description adds the crucial consequence the annotations cannot express: Jobinja notifies the candidate, so this is externally visible and irreversible in a human sense. It further discloses that dry_run populates the form without submitting, which is meaningful behavioral context beyond the hints.

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?

Three short sentences, front-loaded with the action and reason-code source, followed by the side effect and the dry-run option. No filler, and the parenthetical Persian term aids matching against the UI.

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?

With no output schema and six parameters, the description covers the risky and ambiguous parts (notification side effect, message semantics, dry_run) well. It stops short of explaining `page_hint` or what a successful call returns/changes, leaving a small but real gap for a destructive tool.

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 0%, so the description must carry all parameter meaning. It does well for `reason`, `message` and `dry_run`, but says nothing about `post`, `applicant_id`, or `page_hint` (the last being especially opaque — likely a pagination/retry aid). Half the parameters remain undefined in both schema and prose.

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?

States a specific verb and resource ('Mark an applicant as rejected') and immediately pins down the mechanism ('with a reason code from list_rejection_reasons'), which names a sibling tool and disambiguates the input source. An agent can distinguish this from restore_applicant or add_note without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: reason codes come from list_rejection_reasons, and internal commentary belongs in add_note rather than `message` ('not an internal note: use add_note for that'). It also explains when to use dry_run, giving a clear non-destructive trial path.

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