Skip to main content
Glama

save_job_alert

Idempotent

Create and store a recurring public job search alert in a local database to track keyword and location matches daily or weekly.

Instructions

Save a recurring public job search alert to local database.

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": {
      "name": "<name>",
      "kw": "<kw>"
    },
    "name": "save_job_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwYesTarget job title or skill keywords
locNoGeographic location or 'Remote'
freqNoAlert check frequency: 'daily' or 'weekly'daily
nameYesDescriptive name label for this alert (e.g. 'Chennai Python Jobs')

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.8
    • addedInput schema / properties / freq / description
      Added value: +"Alert check frequency: 'daily' or 'weekly'"
    • addedInput schema / properties / kw / description
      Added value: +"Target job title or skill keywords"
    • addedInput schema / properties / loc / description
      Added value: +"Geographic location or 'Remote'"
    • addedInput schema / properties / name / description
      Added value: +"Descriptive name label for this alert (e.g. 'Chennai Python Jobs')"
  2. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and locality are largely covered. The description adds that persistence is to a local database, but says nothing about what happens when an alert with the same name already exists, despite the idempotent hint.

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?

A single front-loaded sentence with no filler clauses. The only questionable element is the vague word 'public', which occupies space without conveying actionable meaning.

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?

An output schema and full parameter docs exist, so the description needn't cover return values or field semantics. However, for a create-style tool it omits duplicate/overwrite behavior and what 'public' constrains, which an agent would need to call it confidently.

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 100% with all four parameters documented, including the freq enum and loc default. The description adds no extra meaning about how kw, loc or name interact or how they map to the saved alert, so the schema does all the work.

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: saving a recurring job search alert, with the storage target ('local database') called out. It is distinguishable from siblings like get_saved_alerts and check_saved_alerts, though the qualifier 'public' is ambiguous and unexplained.

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

Usage Guidelines2/5

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

The description never states when to create an alert versus when to use get_saved_alerts or check_saved_alerts, nor any preconditions (e.g., an existing search to base the alert on). Usage is only inferable from the tool name.

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