Skip to main content
Glama

Pass on a job listing

passJob
Idempotent

Hide a job board listing the candidate isn't interested in, so searchJobs stops showing it, the same as pass on the dashboard's job board.

Passing is private. The company never hears about it, and it only affects job board listings; a Clera match goes to declineMatch instead.

Pass position and companyName exactly as the search result gave them. They are checked against the record, so a mismatch is refused rather than hiding the wrong role. Passing the same listing twice changes nothing; unpassJob brings one back.

When the candidate said why, pass reasonCode (salary_expectations (the comp is too low for them), location_mismatch (the location or remote setup doesn't work for them), visa (they need a sponsorship or work permit the role can't give), company_mismatch (they don't want this company), role_mismatch (not the kind of role they do), seniority_mismatch (too junior or too senior for them), candidate_not_searching (not looking right now), other (anything else, in their words)) and their words in reasonNote. Leave both out when they gave no reason; never guess 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>",
      "position": "<position>",
      "companyName": "<companyName>"
    },
    "name": "passJob"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId from a searchJobs result, or a readJobListing result with kind board.
positionYesThe position exactly as the result gave it.
reasonCodeNoWhy the candidate passed, only when they said.
reasonNoteNoThe candidate's reason in their own words.
companyNameYesThe company name exactly as the result gave it, or null when it had none.

Output Schema

NameRequiredDescriptionDefault
jobIdYes
positionYes
companyNameYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations, the description discloses privacy ('the company never hears about it'), scope (only job board listings), validation behavior (position/companyName mismatch is refused), and reason-handling rules. These details materially inform safe invocation, even though idempotency is also in annotations.

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?

The description is front-loaded with the core action, then structured into privacy/scope, identifier validation, idempotency/reversal, and reason handling. The length is justified by the enum meanings and validation rules, and no sentence is merely repetitive.

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 mutation tool with five parameters, enum choices, validation rules, and an output schema, the description covers everything an agent needs to invoke it correctly. Return values are handled by the output schema, so their absence from the description is appropriate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is already 100%, the description adds substantial meaning: it explains why position and companyName must match exactly, clarifies when to omit reasonCode and reasonNote, and gives per-value semantics for each reasonCode. This goes well beyond the schema's parameter 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?

The description states a specific verb and resource: hide a job board listing the candidate isn't interested in so searchJobs stops showing it. It distinguishes the action from declineMatch for Clera matches and from unpassJob for reversal, so an agent can identify the exact operation without opening other schemas.

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?

It gives clear when-to-use guidance for job board listings and explicitly routes Clera matches to declineMatch instead. It also covers idempotency and reversal via unpassJob, leaving little ambiguity 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