Skip to main content
Glama
jobhunt

jobhunt

by athulanish

list_jobs

Retrieve jobs from a private application tracker, optionally filtered by status such as saved, applied, interview, offer, rejected, or withdrawn.

Instructions

List jobs in the tracker, optionally filtered by status: saved, applied, interview, offer, rejected, withdrawn.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, yet it never states that this is a read-only, non-mutating operation, nor anything about result size, ordering, pagination, or what happens with an empty status. The only behavioral fact conveyed is that the filter is optional.

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?

One front-loaded sentence with no filler; the action comes first and the filter values follow. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema, the description covers the filter domain adequately but omits the default/empty-status behavior and any sense of the returned collection. It is minimally sufficient rather than complete.

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 0% and the status parameter has no enum defined, so the description's enumeration of saved, applied, interview, offer, rejected, withdrawn is the only place the agent can learn valid values — a substantial contribution. It stops short of explaining that an empty string (the schema default) means unfiltered.

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?

States a specific verb and resource ('List jobs in the tracker') plus the filter dimension, so an agent knows exactly what the tool returns. It does not distinguish itself from siblings like search_company_jobs or get_job, leaving the agent to infer that this is the plain enumeration over the user's own tracker.

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?

'Optionally filtered by status' implies the no-arg call lists everything, which is useful usage signal. There is no explicit when-to-use/when-not guidance and no mention of when to prefer search_company_jobs or get_job instead, so routing must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.