Job Tracker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_applicationB | Add a new job application to the tracker. |
| update_statusB | Update the pipeline status of an existing application. |
| list_applicationsA | List job applications, optionally filtered by status, newest first. |
| add_followupB | Schedule a follow-up reminder tied to an application. |
| get_pending_followupsA | List follow-ups due on or before the given date that are not done. |
| mark_followup_doneB | Mark a follow-up reminder as completed. |
| pipeline_summaryA | Return counts of applications grouped by pipeline status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| pipeline_stages |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: application creation/status/list, follow-up creation/listing/completion, and pipeline summary. There is no overlap between the application and follow-up subdomains.
All tool names follow a clear verb_noun pattern with snake_case (e.g., add_application, list_applications, mark_followup_done). The consistency makes the toolset predictable and easy to navigate.
Seven tools is a well-scoped count for a job tracker. Each tool covers an essential operation, and the number feels neither excessive nor sparse for the domain.
The toolset covers the core lifecycle: adding applications, updating status, listing with filters, and follow-up management. It lacks a delete application or update application details, but these are minor gaps that can be worked around.