Skip to main content
Glama

searchnapply

This connector has been deprecated

Replaced by searchnapply.

Deprecated.

Update a job monitor

monitor_update
DestructiveIdempotent

Purpose: Change a saved monitor without losing what it collected or what the user decided; send only what changes, since everything else stays as saved. When: The user wants a different title, location, company, keyword or field on a saved monitor. Cost: About 160 tokens for the saved monitor.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companies": [
        "Contoso"
      ],
      "monitorId": 12
    },
    "name": "monitor_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsNoWords that must appear in the posting's text.
companiesNoCompany names; a posting from any of them is kept, and leaving them out watches the whole market.
locationsNoReal location names, each read as the closest known location; check monitor.locations in the result for what it watches.
monitorIdYesThe monitor id from monitor_list.
salaryMaxNoHighest yearly salary to keep, in US dollars after the same conversion.
salaryMinNoLowest yearly salary to keep, in US dollars after each posting's published salary is converted.
titleTextNoWords of the job title, matched to one of searchnapply's known roles (resolvedRole.display names it), which the monitor then watches.
datePostedNoHow recently the posting was published; leave it out for any date.
departmentNoOne department slug, to narrow a title that spans departments; call job_postings_search_fields for what each one holds.
experienceNoExperience level to keep, given as exact, since a monitor keeps one level and no lowest level.
includeFamilyNoAlso return postings from the resolved role's wider family; leave it out to keep the monitor's current setting.
locationTypesNoWorkplace types to keep.
employmentTypeNoEmployment type to keep.
salaryCurrencyNoA three-letter currency code that only labels the monitor.
excludeKeywordsNoWords that must not appear in the title or the text, 1 to 10 words.
includeNoSalaryNoKeep postings that publish no salary; true by default.

Output Schema

NameRequiredDescriptionDefault
monitorYesThe monitor as saved.
titleNoteNoPresent when no role matched: the title words are matched against posting titles.
resolvedRoleNoThe role the title words were read as; absent when no role matched.
unrecognizedLocationsNoThe location names that matched no known location and were left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / locations / description
      Previous value: -"Real location names in plain words, each read as the closest known location, so check monitor.locations in the result for what it watches."New value: +"Real location names, each read as the closest known location; check monitor.locations in the result for what it watches."
    • changedInput schema / properties / titleText / description
      Previous value: -"Words of the job title, matched to one of searchnapply's known roles when one fits (resolvedRole.display names it), which the monitor then watches, and otherwise matched against posting titles."New value: +"Words of the job title, matched to one of searchnapply's known roles (resolvedRole.display names it), which the monitor then watches."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description explicitly explains the core behavioral trait of the tool: it is a 'patch' operation. By stating it will 'send only what changes' and won't 'los[e] what it collected,' it informs the agent about the non-destructive nature of the update beyond what the annotations suggest.

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?

The definition is highly efficient. The structure flows logically from purpose to usage and cost, ensuring that every sentence serves a vital, distinct purpose in educating the agent.

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?

The definition is complete for an update tool. It covers the operational intent, the required conditions for use, and the behavioral constraints (patch update), ensuring the agent has all necessary context before invocation.

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?

While the input schema coverage is 100%, the description adds significant semantic value by grouping the 16 parameters into logical user changes: 'title, location, company, keyword or field.' This provides immediate, high-level context for the complex parameter list.

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 clearly defines the action as 'Change a saved monitor,' specifying that it operates on an existing resource to modify its settings rather than creating a new one. This distinguishes it from monitor_create and monitor_new.

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?

The 'When' section provides an exhaustive, explicit list of user motivations (different title, location, company, keyword, or field) that triggers the use of this tool. This leaves zero ambiguity about the primary use case.

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