xing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XING_MCP_CACHE_TTL | No | Response cache TTL in seconds | 300 |
| XING_MCP_RATE_LIMIT | No | Minimum seconds between requests | 1.0 |
| XING_MCP_USER_AGENT | No | Override the User-Agent | honest self-identifying UA |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Search job postings on XING, the main professional network in the DACH region (Germany, Austria, Switzerland). Most listings include a salary estimate, which is unusual for job boards. Args:
keywords: Job title or skills, e.g. "python developer". German terms
often match better for DACH roles ("Softwareentwickler").
location: City or region, e.g. "Berlin", "München", "Wien".
radius: Search radius around Returns a dict with |
| search_jobs_paginatedA | Search XING jobs across multiple pages, deduplicated. Use this instead of calling Args: keywords: Job title or skills. location: City or region. radius: Search radius in kilometres. employment_type: FULL_TIME or PART_TIME. max_results: Maximum jobs to return (capped at 200). |
| get_job_detailsA | Fetch the full details of one XING job posting, including the complete description converted to markdown. Args: identifier: A XING job URL, or the slug from one (e.g. "berlin-python-developer-financial-services-156675213"). description_max_chars: Truncate the description beyond this length. |
| get_company_jobsA | List the open positions published on a company's XING page. Args: company: The company's XING page slug or full page URL — the part after /pages/, e.g. "exxetaag" for xing.com/pages/exxetaag. |
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 4 tools
Each tool has a clearly distinct purpose: search for jobs, get job details, search across pages, and get company jobs. The two search tools are differentiated by pagination and deduplication, with clear guidance to prefer the paginated one for multi-page queries.
All tools follow the verb_noun pattern with consistent snake_case: search_jobs, search_jobs_paginated, get_job_details, get_company_jobs. This makes the tool set easy to predict and navigate.
Four tools is well-scoped for a job search server, covering search, detail retrieval, pagination, and a company filter without redundancy or bloat.
The domain of job searching is well covered: searching with filters, pagination, job details, and company-specific listings. Minor gaps like browsing by category or filtering by salary range exist, but the core workflow is complete.