Skip to main content
Glama
Sign In
jobwatch

jobwatch

by vinayvobbili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_jobs

Read-onlyIdempotent

List tracked job postings by status, newest first, including closed roles. Use it to review all jobs in a given status, such as skipped or applied, before deciding next steps.

Instructions

Tracked jobs with their tracking fields, newest first, including closed postings. A plain list by status (e.g. every skipped job); for ranked new jobs use get_digest, for the next to apply to list_queued_jobs, and for follow-ups list_applications.

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
statusNoOnly jobs with this status; omit for all.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • changedInput schema / properties / status / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "new",
+      "shown",
+      "queued",
+      "applied",
+      "screening",
+      "interviewing",
+      "offer",
+      "rejected",
+      "withdrawn",
+      "skipped"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / status / description
      Added value: +"Only jobs with this status; omit for all."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds genuine behavioral context with 'newest first' ordering and the fact that closed postings are included, which is non-obvious for a job list. Pagination/limits are not addressed, but an output schema exists to carry return-shape details.

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?

Two sentences, zero filler; the core behavior (untracked plain listing) is front-loaded before the disambiguation list. Every clause earns its place.

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?

With annotations covering safety, a 100%-covered single enum parameter, an output schema handling return values, and clear sibling routing, nothing an agent needs to call this correctly is missing.

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 100% and the sole status parameter is fully described with its enum in the schema, so the baseline is 3. The description adds meaning by illustrating the filter's intent ('a plain list by status, e.g. every skipped job'), clarifying that it is an unranked equality filter rather than a relevance query.

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 ('tracked jobs'), plus scope qualifiers: newest-first ordering, inclusion of closed postings, and 'tracking fields'. It actively distinguishes itself from sibling list tools rather than restating the name.

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?

Explicitly names three alternatives (get_digest, list_queued_jobs, list_applications) with the condition that selects each, and adds a plain-list use case ('every skipped job'). An agent can route without opening any schema.

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

Deploy Server

Other Tools