Skip to main content
Glama

Update posting

hunt_update_posting
Destructive

Patch a posting. Only the fields you pass change. Corrections from real sources only (JH-1). Setting the end client late is common and good — it comes off the due list (JH-5). Effects: posting updated.

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": {
      "posting_id": "<posting_id>"
    },
    "name": "hunt_update_posting"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPosting URL.
titleNo
req_idNoRequisition id exactly as printed, e.g. 151469BR.
sourceNoHow it reached us.
jd_textNoFull JD text, verbatim. Feeds search and the duplicate guard.
comp_maxNoAnnualized. In cents (integer minor units) — 1250 means $12.50.
comp_minNoAnnualized. Hourly: annualize ×2080 and say so in comp_notes (JH-11). In cents (integer minor units) — 1250 means $12.50.
locationNo
red_flagsNoe.g. "no comp, no client, registered-agent address".
work_modeNo
comp_notesNoCaveats in prose: "band decorative", "hourly $85 annualized".
end_clientNoThe real client behind an agency posting — key for the duplicate guard (JH-5). Ask for it.
posting_idYesThe posting, e.g. JP-0001.
employment_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a non-read-only, destructive, non-idempotent write; the description adds genuinely useful patch semantics (untouched fields are preserved) plus the business consequence that setting end_client clears the posting from the due list. What remains undisclosed is why destructiveHint is true and what the operation can clobber — "Effects: posting updated." restates rather than informs.

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?

Front-loaded with the core semantics (patch, partial update) in the first two sentences, followed by two short scoping rules. Only "Effects: posting updated." is pure filler; the rest earns its space.

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 14-parameter mutation with no output schema, the description covers the essential semantics (partial update, source-quality rule, end_client consequence) that an agent needs before calling. The main gap is that destructiveHint is never explained, but the schema is rich enough that this is a minor omission.

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 coverage is 71%, so the schema largely carries parameter meaning on its own (cents-based comp, enum values, req_id format). The description contributes one piece of parameter behavior beyond the schema — the effect of passing end_client — but says nothing about the remaining fields, so it neither fills the coverage gap nor adds much over structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Patch a posting" states a specific verb and resource, and "Only the fields you pass change" immediately clarifies it is a partial update rather than a replace. It stops short of naming a sibling (e.g. hunt_add_posting) to contrast with, so differentiation is only implicit.

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

Usage Guidelines3/5

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

The definition conveys when this is appropriate indirectly: corrections sourced from real sources (JH-1), and late assignment of the end client (JH-5). But it never states when to use it versus hunt_add_posting or hunt_correct_application, and the JH codes are unexplained shorthand an agent may not resolve.

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.