Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Turn off a job alert

delete_job_alert
Destructive

Turn off one alert by alertId.

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": "delete_job_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alertIdYesAlert ID from list_job_alerts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds nothing beyond that: it doesn't say whether 'turn off' deletes the alert or merely disables it, whether the change is reversible, or that the effect is external. It also uses 'turn off', which sounds idempotent, while annotations declare idempotentHint=false, so the description adds no clarity exactly where it is most needed.

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?

The description is a single eight-word sentence with no wasted words and the identifying parameter placed last. It is well structured, but its brevity comes at the cost of the behavioral detail the definition lacks.

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 one-parameter tool with full schema coverage and rich annotations, this is almost, but not quite, adequate: the one missing piece is what 'turn off' actually does to the alert and whether it can be undone. Because annotations already carry the safety profile for scheduling, the remaining gap is small.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents alertId, including that it comes from list_job_alerts. The phrase 'by alertId' merely restates the schema, which sets a baseline of 3.

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 concrete verb ('Turn off') with a specific resource ('one alert') and the key that selects it ('by alertId'). An agent knows exactly what the call does, though it gives no hint about how this differs from update_job_alert, and it leaves a slight gap between 'turn off' and the tool name delete_job_alert.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as update_job_alert for editing an alert versus turning it off. Usage is only implied by the verb.

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.