Skip to main content
Glama

List tracked jobs

get_recent_vacancies
Read-only

List the user's tracked vacancies, pinned first (is_pinned), then newest by analyzed_at: finished fit analyses (match percentage, verdict, key strengths and gaps) and vacancies tracked without an analysis (analysis_status 'none', match fields null). Vacancies with an analysis still running or failed are not listed. Filters: tracker status, analysis_status. total says how many match in all. Default limit 10, max 50. Empty list is a normal result.

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": "get_recent_vacancies"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNo

Output Schema

NameRequiredDescriptionDefault
totalNoHow many vacancies match in all; vacancies holds at most limit of them.
vacanciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / $defs / VacancyItem / properties / verdict_category / description
      Previous value: -"One of 'apply' | 'consider' | 'skip' | 'not_eligible' | 'invalid', or null if not categorized. 'not_eligible' means a hard eligibility blocker applies — the user cannot take this role as posted no matter how high match_percentage is; eligibility_blockers carries the reason."New value: +"One of 'apply' | 'consider' | 'skip' | 'not_eligible' | 'confirm_status' | 'invalid', or null if not categorized. 'not_eligible' means a hard eligibility blocker applies — the user cannot take this role as posted no matter how high match_percentage is; eligibility_blockers carries the reason. 'confirm_status' means the posting requires a status the user has not stated, so the verdict is open until they answer the blocker's question."
  2. Changed2 schema fields changed
    • changedOutput schema / $defs / VacancyItem / properties / analyzed_at / description
      Previous value: -"ISO 8601 timestamp."New value: +"ISO 8601 timestamp of when the vacancy was analyzed or, if never analyzed, added."
    • addedOutput schema / $defs / VacancyItem / properties / is_pinned
      Added value: +{
      +  "default": false,
      +  "description": "The user pinned it to the top of their tracker; lists put pinned vacancies first.",
      +  "title": "Is Pinned",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the read-only/non-destructive profile, and the description layers on real behavioral detail: result ordering and tiebreak, which records are filtered out server-side, that match fields are null for unanalyzed entries, that total is an unfiltered-by-limit count, and the default/capped limit. That is exactly the context annotations cannot express.

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?

Front-loaded with the core action and ordering, then filters, then limits — a sensible priority order. The first sentence is long and run-on with parenthetical field lists, but nearly every clause carries operational information rather than filler.

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?

With an output schema present, the description need not explain return values, yet it still signals which fields come back. The main completeness gap is the undocumented archived parameter, which changes result semantics in a way an agent could easily miss given the schema's top-level coverage is weak.

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?

The description restates limit (default 10, max 50) and names the status and analysis_status filters, largely duplicating the nested schema descriptions. It never mentions the 'archived' parameter, which is a meaningful behavioral switch (default false hides archived vacancies; only archived ones can be deleted). Baseline 3 for schema-documented params, minus the omission.

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?

Specific verb + resource with scope: 'List the user's tracked vacancies', plus the ordering rule (pinned first, then newest by analyzed_at). The term 'tracked' separates it from search_vacancies/get_vacancy_detail, but no sibling is named explicitly, so an agent must infer the boundary from vocabulary alone.

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

Usage Guidelines4/5

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

Gives clear usage context: two supported filters, an explicit exclusion ('vacancies with an analysis still running or failed are not listed'), and a normalization hint ('empty list is a normal result'). It stops short of routing to alternatives — nothing says when to prefer get_vacancy_detail, search_vacancies, or list_offers over this.

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.