Skip to main content
Glama

BirJob

Delete a saved job search

delete_job_alert
DestructiveIdempotent

Delete one of the user's saved searches. Use this only when the user asks to stop following a search. Cannot be undone; the search can be saved again with create_job_alert. Needs a signed-in BirJob job seeker account: the first call asks the user to sign in to BirJob and allow access.

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": {
      "alert_id": "<alert_id>"
    },
    "name": "delete_job_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesThe id from get_job_alerts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, but the description adds material behavior beyond them: the deletion is irreversible, the search can be recreated via create_job_alert, and the first call triggers a sign-in/consent flow for a BirJob job seeker account. The auth-flow disclosure is exactly the kind of non-schema behavior an agent needs before invoking.

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?

Three short sentences ordered by importance: what it does, when to use it, then consequences and prerequisites. No redundant restatement of the title or annotations.

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?

For a single-parameter destructive tool with no output schema, the description covers the action, the trigger condition, irreversibility, the recovery path, and the auth prerequisite. Nothing an agent needs to call it safely is missing.

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?

The single alert_id parameter is fully documented in the schema, including its provenance ("The id from get_job_alerts") and integer constraints, so the description need not repeat it. It adds nothing further about the identifier, which is acceptable at 100% schema coverage but is only baseline value.

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 ("Delete one of the user's saved searches") and implicitly contrasts with the creation sibling by naming create_job_alert as the way to re-save. An agent can distinguish this from get_job_alerts or create_job_alert without reading either schema.

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?

Gives an explicit positive condition ("only when the user asks to stop following a search") plus the inverse action to point users at (create_job_alert) if they change their mind. The restrictive "only when" is a genuine exclusion, not just implied context.

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