Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Close, reopen or extend a job

update_job_status
Destructive

Closes a job (removes it from search), reopens it within the plan's active-job limit, or extends its expiry by a number of days.

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": {
      "jobId": "<jobId>",
      "action": "<action>"
    },
    "name": "update_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays to extend/reopen for (1-90, default 30).
jobIdYesJobiba job ID (the id field from search_jobs or list_my_jobs).
actionYesWhat to do.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's added value is the specific consequence set: closing removes the job from search results, reopening only succeeds within the plan's active-job limit, and extend is bounded by a day count. That is meaningful behavioral context beyond the annotations. It omits whether closing affects existing applicants or is reversible without limit, leaving a small gap.

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?

A single sentence enumerating the three actions with their effects, zero filler, and the most consequential behavior (removal from search) is stated first. Nothing redundant with the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation tool with no output schema, the description covers what each action does but says nothing about the response, whether closing is silently reversible, or what happens if reopen exceeds the active-job limit. Adequate to invoke, thin on consequences an agent should anticipate.

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 is 100%, so jobId sourcing, the action enum and the 1-90 days range are already documented in the schema. The description only reinforces that 'days' governs the extend/reopen duration and that the plan's active-job limit gates reopen, which is marginal added meaning. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource (job status) and spells out the three distinct actions with their effects: close removes the job from search, reopen is bounded by the plan's active-job limit, extend pushes the expiry out by days. An agent knows exactly what will change. It stops short of naming a sibling such as edit_job, so differentiation is only implicit through the action enum.

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 three action outcomes imply when each applies (taking a job down, bringing it back, keeping it live), but there is no explicit statement of when to prefer this over edit_job or post_job, and no stated preconditions or failure modes. Usage is inferable rather than guided.

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.