Skip to main content
Glama

Market Data

by com.timzinin.api

XING Jobs (DACH) Scraper

xing-jobs
Read-only

Walk xing.com's own job sitemap and pull public job listings from Germany/Austria/Switzerland: title, company, location, employment type, posted date, industry, and (optionally) the full description — straight from each job's own public page. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_itemsNoHow many job rows to deliver, at most. This Actor walks xing.com's own job sitemap and visits each candidate job page individually — a meaningful share of freshly-listed jobs are already withdrawn (HTTP 410) by the time they're visited, which is normal churn, not a fault. Extra candidates are attempted automatically to compensate, so this number is a target, not a guarantee.
freshness_daysNoSkip sitemap entries older than this many days. In practice xing.com's own sitemap entries are typically only minutes to hours old at any given time, so this rarely filters anything out.
keyword_filterNoOptional case-insensitive substring match against each job's title, applied on this Actor's side after fetching the job's own page. xing.com's job search itself needs a browser session and is not used here — there is no server-side keyword search on this Actor. Leave empty to keep every job found.
sitemap_override_urlNoAdvanced: override the internal xing.com jobs sitemap URL this Actor walks. Leave empty to use the live xing.com jobs sitemap index. Mainly useful for diagnostics.
fetch_full_descriptionNoInclude the job's full description text in the output row. This Actor already fetches each job's own page to get any data at all (title, company, location...), so the description costs no extra request either way — this setting only controls whether it's kept in the row.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it as read-only and non-destructive, but the description adds meaningful context: it walks the sitemap, visits each job page, handles HTTP 410 churn by compensating with extra candidates, and discloses the cost per call. This goes well beyond the annotations.

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?

The description is a single, information-dense sentence that front-loads the action and includes essential details (fields, method, cost) without any redundant words. Every part adds value.

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 no output schema, the description lists all returned fields, explains the crawling mechanism, and describes fault behavior (410 churn and compensation). This is fully sufficient for an agent to understand the tool's scope and behavior.

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?

Input schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The tool description adds minimal parameter-specific meaning (e.g., optional full description aligns with fetch_full_description) but does not extend beyond the schema's own richness.

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?

The description clearly states it walks xing.com's job sitemap and pulls public job listings from Germany/Austria/Switzerland, with a specific verb and resource. It also lists fields returned, distinguishing it from sibling job scrapers by site and region.

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?

The description provides clear context for when to use the tool (scraping XING DACH jobs) but does not explicitly mention alternatives or exclusions. It is easy to infer when to use it, though it lacks explicit 'when not to use' guidance.

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

All Market Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

Many tools are distinct by region/source (e.g., otodom-warsaw vs. imovirtual-lisbon), but there are overlapping categories: multiple real estate, job, SEC, and crypto tools. Watchers/alerts (job-alert, re-new-listing-alert, tender-alert) could be confused with their corresponding search tools, and token tools (live-price-oracle, token-launch-radar, rug-pull-scorer) have similar purposes.

Naming Consistency2/5

Names follow no consistent pattern: some are hyphenated source-location (emlakjet-istanbul), some are generic descriptors (job-alert, pricing_info uses underscore), and some are verbose phrases (official-gazette-regulatory-action-router). There is no consistent verb_noun or noun structure, making it hard to predict what a tool does from its name.

Tool Count2/5

With 36 tools, the server is in the 'too many' range (25+). The broad 'Market Data' theme partially justifies the count, but it feels bloated with many single-country listings and overlapping watchers that could be consolidated.

Completeness3/5

The domain is loosely defined as 'market data,' spanning real estate, jobs, tenders, SEC filings, crypto, and clinical trials. While it covers niche areas well, there are notable gaps: no general stock/ETF quotes, no forex/commodities data, and no cross-country aggregate search. The mix of scrapers and alerts leaves the surface feeling uneven.

Resources