Skip to main content
Glama

Skip job

skip_job
DestructiveIdempotent

Record that the user is passing on a Himalayas job, with the reason, so it stops coming back in get_new_matches and future matches can learn from it. job_closed also reports the listing as expired. For a job already in the tracker, use update_job_status with outcome didnt_apply instead. Uses the connected Himalayas account; no extra sign-in needed.

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": {
      "company_slug": "<company_slug>",
      "job_slug": "<job_slug>",
      "reason": "<reason>"
    },
    "name": "skip_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoAnything worth knowing, in a sentence or two (what the page said, a hidden requirement). No personal data.
reasonYesWhy the user is passing on it
job_slugYesJob slug (from the job listing URL)
company_slugYesCompany slug (from the job listing URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=true, so the safety profile is covered. The description adds non-obvious behavior: the skip suppresses future matches and feeds match learning, job_closed additionally reports the listing as expired, and no separate sign-in is required. It stops short of describing the tool's response or whether a skip can be undone.

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 sentences, each carrying distinct load: what the tool does and its effect, the special-case reason, the alternative route, and the auth note. Purpose is front-loaded and there is no filler or restatement of the title.

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?

For a four-parameter mutation tool with full schema coverage, no output schema, and annotations covering safety, this is close to complete: effects, alternative routing, and auth are all covered. Minor gaps remain around confirmation/return behavior and whether a skip is reversible, which an agent may want to know.

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 description coverage is 100%, so the baseline is 3; the description earns an extra point by attaching semantics to a specific enum value (job_closed reports the listing as expired) and by emphasizing that a reason is mandatory, which is behaviorally meaningful beyond the bare 'Why the user is passing on it' schema text.

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 ('Record that the user is passing on a Himalayas job'), names the observable effect ('stops coming back in get_new_matches'), and distinguishes itself from update_job_status by scope. An agent can separate it from save_job / remove_saved_job / update_job_status without opening any 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 alternative with the selecting condition: 'For a job already in the tracker, use update_job_status with outcome didnt_apply instead.' It also clarifies the job_closed reason's extra side effect, so the agent knows when a plain skip is insufficient.

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