Skip to main content
Glama

check_saved_alerts

Read-onlyIdempotent

Run saved LinkedIn search alerts against live results to detect and report new matches. Check all alerts or specify IDs to find job postings you haven't seen yet.

Instructions

Run saved alerts against live LinkedIn search and report newly discovered matches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_saved_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoOptional list of specific alert IDs to check. If omitted, checks all saved alerts.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / ids / description
      Added value: +"Optional list of specific alert IDs to check. If omitted, checks all saved alerts."
  2. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false. The description usefully adds that execution hits live LinkedIn search and yields only 'newly discovered' matches, but omits rate limits, latency, and whether matched alerts are marked as processed.

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?

One sentence, front-loaded with the action and ending on the deliverable. Nothing wasted, no filler.

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?

The tool is simple (one optional array param, output schema present), and annotations plus output schema carry most of the burden. What remains thin is operational context for an open-world call that scrapes live LinkedIn data — expected duration, cost, and whether repeated runs deduplicate.

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% and the single 'ids' parameter is fully documented in the schema, including the omit-to-check-all default. The description adds nothing about 'ids' and repeats the all-alerts default implicitly, so baseline 3 applies.

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?

The description pairs a specific verb ('Run saved alerts') with a concrete outcome ('report newly discovered matches') and names the external source (live LinkedIn search). It is clearly distinct from sibling get_saved_alerts (which lists alerts) and save_job_alert, though it never names those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the tool to re-run stored alerts and surface new results, but there is no explicit 'use when' statement, no exclusion of get_saved_alerts, and no note on how often it should be called.

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