Skip to main content
Glama

Remove a saved job listing

unsaveJob
DestructiveIdempotent

Remove a job board listing from the saved list.

Removing one that was never saved returns not_saved and changes nothing — that is not an error worth apologising for.

This only drops the bookmark. It does not withdraw an application, because Clera never sent one.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "jobId": "<jobId>"
    },
    "name": "unsaveJob"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId from a listSavedJobs result.

Output Schema

NameRequiredDescriptionDefault
jobIdYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real context beyond them by naming the not_saved outcome and explaining that the effect is bookmark-only, which reframes the "destructive" flag as low-impact. It also discloses that inputs and results are recorded for tracking and support. It does not cover auth/prerequisite requirements, keeping it at 4 rather than 5.

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 core operation is front-loaded in the first line and the following paragraphs each address a distinct concern (no-op behavior, scope boundary, data logging) with no repetition. The data-recording sentence is somewhat boilerplate, which keeps it from a 5.

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 tool with full annotations and an output schema, the description covers everything an agent needs: the effect, the idempotent no-op case, the scope boundary against application deletion, and the privacy note. Return values need not be explained because an output schema exists.

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 jobId parameter is documented there as coming from a listSavedJobs result. The description adds no additional meaning about the parameter (no format, no validation, no sourcing caveats beyond what the schema states), so the baseline 3 applies.

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?

"Remove a job board listing from the saved list" gives a specific verb (remove) and resource (saved job listing), and the follow-up sentence "This only drops the bookmark. It does not withdraw an application" explicitly separates it from application-deletion tools such as deleteApplication. An agent can identify the operation and its boundary without opening the schema.

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

Usage Guidelines4/5

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

The description establishes clear context for use (undo a save) and pre-empts the most likely confusion by stating the tool does not affect applications. It also sets expectations for the no-op case. It stops short of naming saveJob/unpassJob as the inverse operations, so guidance is strong but not fully explicit about alternatives.

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