Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Change a job alert

update_job_alert
Destructive

Change one of the user's own job alerts by alertId: pause or resume it, daily or weekly, its location, and its filters (work mode, job type, level, minimum annual pay + currency). Send only the fields to change; an empty string clears a filter or the location. Answers the alert as stored, how many live jobs added in the last 7 days match it now and up to 3 of them.

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": {
      "alertId": "<alertId>"
    },
    "name": "update_job_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedNotrue = pause, false = resume.
alertIdYesAlert ID from list_job_alerts.
jobTypeNoJob type.
currencyNoCurrency for the salary filter.
locationNoCity, region or country; empty = no place.
frequencyNoHow often.
remoteTypeNoWork mode.
experienceLevelNoLevel.
minAnnualSalaryNoMinimum annual salary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: annotations only declare readOnly=false, destructive=true, idempotent=false, openWorld=true, but the description adds patch semantics, the empty-string clear behavior, the ownership restriction, and the response payload (stored alert, live-match count for the last 7 days, up to 3 sample jobs). Nothing contradicts the destructiveHint, which the clearing behavior is consistent with.

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?

Two dense sentences, front-loaded with the verb/resource/mutable-fields and followed by the patch and return-value rules. The final clause ('Answers the alert as stored, how many live jobs...') is compressed enough to read awkwardly, but no sentence is wasted.

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

Completeness5/5

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

No output schema exists, yet the description explains the return value, and for a 9-parameter mutation it covers patch semantics, clearing, ownership, and response shape. An agent has everything needed to call it correctly.

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 genuinely new meaning: that fields are optional and omitted fields are left unchanged, and that empty strings clear filters (the schema only states this for location). It does not restate the enum values or the currency/salary coupling beyond naming them.

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 ('change one of the user's own job alerts by alertId') and enumerates exactly what is mutable: pause/resume, frequency, location, and filter set. The ownership scoping ('the user's own') and patch semantics distinguish it from create_job_alert and delete_job_alert without naming them.

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?

Gives clear operational guidance on partial updates ('Send only the fields to change') and on removal ('an empty string clears a filter or the location'), which is the main ambiguity for a patch tool. It stops short of explicitly contrasting with create_job_alert/delete_job_alert or listing prerequisites such as the alert needing to exist.

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.