jobjourney-claude-plugin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port when TRANSPORT=httpStream | 8080 |
| TRANSPORT | No | MCP transport: stdio or httpStream | stdio |
| JOBJOURNEY_API_KEY | No | API key for backend-authenticated features | |
| JOBJOURNEY_API_URL | No | JobJourney backend base URL | https://server.jobjourney.me |
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 |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_jobA | Save a new job application to track. Use this when the user wants to save or add a job they're interested in or have applied to. |
| get_jobsA | Get the user's saved jobs with their current status. Use this to check job application status, list all jobs, or find specific jobs. |
| get_job_detailsA | Get full details of a specific job by ID, including description, skills, notes, and evaluation data. |
| update_job_statusB | Update the status of a job application. Use this when the user's application progresses (got an interview, received offer, was rejected, etc.) |
| delete_jobB | Delete a saved job. Use this when the user wants to remove a job from their list. |
| star_jobC | Star or unstar a job to mark it as important. |
| add_job_noteA | Add a note to a job application. Use this when the user wants to record information about a job (e.g., interviewer name, follow-up date, salary info). |
| update_job_noteC | Update an existing note on a job application. |
| delete_job_noteC | Delete a note from a job application. |
| get_job_evaluationB | Get the saved CV/resume evaluation for a specific job. |
| get_job_cover_letterC | Get the saved cover letter for a specific job. |
| bulk_update_jobsC | Perform bulk operations on multiple jobs at once: delete, reject, or advance to next stage. |
| get_dashboard_statsA | Get an overview of the user's job search progress including job counts by status, scraping metrics, document counts, and feature usage. Great for answering 'how is my job search going?' |
| evaluate_job_fitB | Use AI to evaluate how well the user's profile/resume matches a specific job. Returns a fit score and detailed analysis. |
| generate_cover_letterB | Use AI to generate a tailored cover letter for a specific job based on the user's profile/resume. |
| generate_interview_questionsB | Use AI to generate practice interview questions for a specific job. Choose between technical or behavioral questions. |
| conduct_mock_interviewC | Conduct an AI-powered mock interview for a specific job. Simulates a real interview experience. |
| get_mock_interview_reportC | Get the mock interview report for a specific job. |
| generate_coffee_chat_suggestionsC | Use AI to generate personalized coffee chat introduction messages based on a person's profile. |
| find_coffee_contactsB | Find people available for coffee chats / networking. Use this when the user wants to connect with professionals, find mentors, or network in a specific industry. |
| send_coffee_chat_requestA | Send a coffee chat request to a user. Use this after finding contacts with find_coffee_contacts. |
| get_coffee_chat_requestsB | Get the user's coffee chat requests - either sent or received. |
| get_my_coffee_profileB | Get the user's own coffee chat profile. |
| update_coffee_profileC | Create or update the user's coffee chat profile to make themselves available for networking. |
| delete_coffee_profileA | Delete the user's coffee chat profile, removing them from the networking pool. |
| respond_coffee_chatC | Accept or decline a received coffee chat request. |
| get_coffee_chat_messagesC | Get messages in a coffee chat conversation. |
| send_coffee_chat_messageC | Send a message in a coffee chat conversation. |
| get_coffee_chat_statsB | Get coffee chat statistics (requests sent, received, accepted, etc.). |
| get_notificationsB | Get the user's notifications. Use this when the user asks about updates, alerts, or what's new. |
| mark_notifications_readB | Mark all notifications as read. |
| get_unread_notification_countB | Get the count of unread notifications. |
| mark_notification_readC | Mark a single notification as read. |
| delete_notificationC | Delete a notification. |
| get_profileB | Get the user's profile information including skills, experience, education, and projects. |
| update_profile_basicC | Update basic profile information (name, headline, bio, location). |
| update_profile_skillsC | Update the user's skills list. |
| update_profile_employmentC | Update the user's employment history. |
| update_profile_educationC | Update the user's education history. |
| update_profile_projectsC | Update the user's projects. |
| update_profile_referencesC | Update the user's references. |
| update_full_profileB | Update the entire user profile at once (all sections). |
| get_public_portfolioB | View someone's public portfolio by their identifier (username or slug). |
| get_documentsB | List all user documents (CVs and cover letters). |
| get_documentC | Get details of a specific document by ID. |
| delete_documentC | Delete a document (CV or cover letter). |
| rename_documentC | Rename a document. |
| get_subscription_statusB | Check the user's current subscription status and plan details. |
| get_subscription_plansB | View available subscription plans and pricing. |
| check_feature_accessB | Check if the user has access to a specific AI feature based on their subscription. |
| get_payment_historyB | View the user's payment history. |
| get_community_commentsC | Browse community posts and comments. |
| get_comment_threadB | View a comment and its replies. |
| create_commentC | Post a new comment in the community. |
| update_commentC | Edit an existing comment. |
| delete_commentC | Delete a comment. |
| generate_cvC | Generate a CV/resume as PDF using AI based on the user's profile. |
| generate_and_store_cvC | Generate a CV and save it to the user's documents. |
| chatB | Send a message to the JobJourney AI chatbot for career advice, job search tips, or general help. |
| get_scraping_statsB | View job scraping statistics from the browser extension. |
| get_scraping_stats_aggregatedC | View aggregated scraping statistics with breakdowns by website and time period. |
| get_portfolio_visitsB | Get the user's portfolio visit count. |
| get_portfolio_analyticsC | Get detailed analytics for a portfolio page. |
| check_for_updatesA | Check whether a newer published version of the local JobJourney plugin is available and show the update command. |
| setup_local_scrapingA | Prepare the local scraping environment. Initializes local SQLite, checks Playwright/browser readiness, starts the background agent if needed, reports login status for supported sites, and returns the next recommended commands. |
| discover_jobsA | Find jobs for the user by scraping live listings from job sites (LinkedIn, SEEK, Jora, etc.). This is the primary tool for job searching — always use this when the user wants to find, search, or look for jobs. Enriches results with ATS detection, expands career pages, stores results locally, then opens the web app for visualization. |
| schedule_jobsA | Schedule recurring job discovery. The jobjourney-agent will run the discovery engine daily at the requested time across all specified sources and store results locally. |
| list_schedulesA | List all scheduled job discovery cron jobs, including disabled ones. Shows schedule ID, keyword, location, sources, cron expression, enabled status, and last run time. |
| toggle_scheduleA | Enable or disable a scheduled job discovery cron job by its ID. The agent will pick up changes on its next reconcile cycle (within 60 seconds). |
| delete_scheduleA | Permanently delete a scheduled job discovery cron job by its ID. Use list_schedules to see available IDs. |
| delete_all_schedulesB | Permanently delete ALL scheduled job discovery cron jobs. Use with caution. |
| get_latest_discovery_reportB | Show a summary of the most recent discovery run, including sources, job count, and the top stored jobs for that run. |
| login_jobsiteA | Open a browser window for the user to log in to a job site (SEEK or LinkedIn). Saves cookies so future scrapes can access full job details including descriptions, salary, and applied status. Run this once per site before scraping. |
| check_login_statusA | Check if cookies exist for job sites. Shows which sites have saved login sessions. |
| open_application_pageA | Open a job application page in the browser. Detects aggregator sites (LinkedIn/Seek/Indeed) and resolves to the real application URL. Keeps the browser open for subsequent form-filling tool calls. |
| extract_form_fieldsA | Extract all visible form fields from the current page. Returns structured data for each field including label, type, options, and a CSS selector for filling. Call open_application_page first. |
| fill_form_fieldA | Fill a single text input or textarea field on the current page. Use the selector from extract_form_fields. |
| select_form_optionA | Select an option in a dropdown, radio group, or checkbox. Tries matching by label text first, then by value. |
| upload_resumeA | Upload a CV/resume file to a file input on the current page. Uses the primary CV by default, or specify a document ID. |
| click_elementA | Click a button or link on the current page (e.g., Next, Submit, Continue). Returns whether the page URL changed or new content appeared. |
| set_default_cvA | Set a CV as the default/primary document for auto-apply resume uploads. |
| take_page_screenshotA | Take a screenshot of the current page for visual inspection. Useful for verifying form state, handling CAPTCHAs, or debugging unusual layouts. |
| close_browserB | Close the browser session and clean up resources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 83 tools
The set covers many distinct domains (job search, applications, profile, networking, community, browser automation), but several tool pairs have overlapping or easily confused purposes, such as generate_cv vs generate_and_store_cv, get_documents vs get_document, mark_notifications_read vs mark_notification_read, and evaluate_job_fit vs get_job_evaluation. Descriptions help, but the sheer number of tools increases misselection risk.
Almost all tools follow a consistent snake_case verb_noun pattern (get_, update_, delete_, create_, send_, etc.), with a few minor deviations like the bare 'chat' and plural/singular inconsistencies in notification tools. The convention is readable and predictable.
83 tools is far beyond the 50+ threshold for extreme mismatch; even for a feature-rich job search plugin, this many tools is excessive and will burden an agent's context and selection process.
The surface covers job discovery, application tracking, profile management, networking, community, documents, subscriptions, and browser automation comprehensively. Minor gaps exist, such as editing saved job details or searching community posts, but core workflows are well supported.