Skip to main content
Glama

Jobiba Hiring

Move an applicant to a stage

update_applicant_status
Destructive

Moves an application to APPLIED, SCREENING, INTERVIEW, OFFERED, HIRED or REJECTED. For most stages the candidate receives the standard Jobiba status email, as in the ATS dashboard. An application the candidate withdrew cannot be moved. An optional note is added to the team's internal notes on the applicant (the candidate never sees it); a note with no status moves nobody and emails nobody.

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": {
      "applicationId": "<applicationId>"
    },
    "name": "update_applicant_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoInternal note for the hiring team, up to 1,000 characters. Never shown to the candidate.
statusNoNew stage.
applicationIdYesApplication ID from list_applicants.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / note
      Added value: +{
      +  "description": "Internal note for the hiring team, up to 1,000 characters. Never shown to the candidate.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "applicationId",
      -  "status"
      -]New value: +[
      +  "applicationId"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses a real side effect the agent would otherwise miss: the candidate receives a standard status email for most stages. It also discloses the withdrawal prerequisite and that notes are internal-only, which together explain what the destructive/non-idempotent hints actually mean in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each carrying information, with the core action and stage list front-loaded. Minor redundancy in re-listing the six enum values that the schema already enumerates, but no padding.

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?

For a three-parameter mutation with no output schema, the description covers action, valid targets, side effects, prerequisites, and the note-only edge case. The only gap is the shape of the response (e.g., whether the new stage or email status is returned).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the note is team-internal and never shown to the candidate, and a note without a status produces no move and no email. That combination behavior is not inferable from the schema alone.

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 opens with a specific verb and resource ('Moves an application') and enumerates the exact destination stages, so the agent knows precisely what the tool does. It is clearly distinguishable from siblings like update_job_status or message_candidate.

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?

It states a concrete precondition ('An application the candidate withdrew cannot be moved') and clarifies the note-only path ('a note with no status moves nobody and emails nobody'). It does not name alternative tools for adjacent needs (e.g., contacting the candidate), but the when-to-use context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources