Skip to main content
Glama

Account Executive Jobs

Remove a saved job

unsave_job
DestructiveIdempotent

Remove one of the signed-in candidate's bookmarks after an explicit request, including a job that is now unavailable. Copy job_slug and saved_at from the exact entry in list_saved_jobs; saved_at distinguishes reused slugs and must stay unchanged on retry. This does not withdraw or delete an application. Exact retries are safe.

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": {
      "job_slug": "<job_slug>"
    },
    "name": "unsave_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_slugYesThe exact savedJobSlug returned by list_saved_jobs, including unavailable jobs.
saved_atNoCopy savedAt from the exact list_saved_jobs entry to remove. Required when a deleted job's slug was reused; preserve it unchanged on retries.

Output Schema

NameRequiredDescriptionDefault
stateYes
messageYes
savedAtYes
savedJobSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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, so the safety profile is covered. The description adds real behavioral detail beyond them: retry semantics ('saved_at ... must stay unchanged on retry. Exact retries are safe') and that currently-unavailable jobs are still removable. It does not contradict any annotation; it slightly enriches the idempotency story rather than merely restating it.

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?

Three tight sentences with the core action front-loaded and the boundary (not an application withdrawal) placed before the retry caveat. It is dense but each clause carries information; the 'Exact retries are safe' fragment is slightly clipped but useful.

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?

An output schema exists, so return-value explanation is unnecessary. The description covers the requirement (explicit request), the correct way to source both parameters, the unavailable-job edge case, the retry/idempotency rule, and the boundary against application withdrawal — everything needed to call this mutation correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it explains that saved_at exists to disambiguate reused slugs and must be carried through unchanged, which is the 'why' behind the parameter rather than a restatement of the schema text. This goes beyond the schema's own field-level descriptions.

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+resource ('Remove one of the signed-in candidate's bookmarks') and scopes it to the signed-in candidate. It explicitly distinguishes itself from the withdraw/delete family ('This does not withdraw or delete an application'), which matters given siblings like withdraw_my_application. An agent can separate this from save_job and the employer-side tools without opening a 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 the trigger condition ('after an explicit request'), the prerequisite source of truth ('Copy job_slug and saved_at from the exact entry in list_saved_jobs'), and an exclusion (it does not withdraw or delete an application). This is explicit when-to-use and when-not-to-use guidance.

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.