Techmap Job Postings MCP Server

Official

by TechMap

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Build an RSS job feed URL

get_rss_feed_url

Read-only

Generate an RSS feed URL for Techmap job postings matching filters. Import jobs into job board software or RSS readers; no API request needed.

Instructions

Build a URL for Techmap's RSS API that returns the postings matching the filters as an RSS 2.0 feed, e.g. to import jobs into job board software (backfill) or an RSS reader. Makes no API request and uses no quota: it only returns the URL, with a {YOUR_RAPIDAPI_KEY} placeholder that the user replaces with a key subscribed to the Techmap RSS API (free plan: 300 postings per month). Use search_jobs instead to see postings in this conversation.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City of the workplace
`state`	No	State/region of the workplace
`title`	No	Search in the job title. Comma = OR, prefix + = must contain, prefix - = exclude, quotes = exact phrase, e.g. "data engineer",-senior (exact phrase "data engineer", excluding senior)
`skills`	No	Skill or keyword, e.g. "python"; same comma/+/- syntax as title
`company`	No	Hiring company name
`industry`	No	Industry, e.g. "healthcare"
`isDirect`	No	Only postings that link directly to the employer
`language`	No	ISO 639-1 language of the posting, e.g. "en"
`workType`	No	fulltime, parttime, flextime …
`hasSalary`	No	Only postings with salary information
`workPlace`	No	remote, hybrid, onsite, field or offshore (use list_filter_values for all values)
`occupation`	No	Occupation stem extracted from the title, e.g. "developer", "nurse"
`countryCode`	No	ISO 3166-1 alpha-2 country code of the job location, e.g. "de", "us", "lu"; "##" for postings without a country (mostly remote). Several codes can be combined with commas, e.g. "de,at,ch"
`dateCreated`	No	Day (YYYY-MM-DD) or month (YYYY-MM) the job was posted. If neither dateCreated nor dateCreatedMin/Max is set, the API uses the day two days ago (the most recent complete day)
`isRecruiter`	No	true = only recruiting firms, false = exclude them
`contractType`	No	permanent, temporary, internship …
`dateCreatedMax`	No	End of a posting date range (YYYY-MM-DD); use together with dateCreatedMin
`dateCreatedMin`	No	Start of a posting date range (YYYY-MM-DD); use together with dateCreatedMax

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	RSS feed URL with a {YOUR_RAPIDAPI_KEY} placeholder
`docs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.0.0Oct 1, 2026

changedInput schema / properties / countryCode / description

Previous value: -"ISO 3166-1 alpha-2 country code of the job location, e.g. \"de\", \"us\", \"lu\""New value: +"ISO 3166-1 alpha-2 country code of the job location, e.g. \"de\", \"us\", \"lu\"; \"##\" for postings without a country (mostly remote). Several codes can be combined with commas, e.g. \"de,at,ch\""

changedInput schema / properties / dateCreated / description

Previous value: -"Day (YYYY-MM-DD) or month (YYYY-MM) the job was posted; defaults to the most recent data"New value: +"Day (YYYY-MM-DD) or month (YYYY-MM) the job was posted. If neither dateCreated nor dateCreatedMin/Max is set, the API uses the day two days ago (the most recent complete day)"

changedInput schema / properties / dateCreatedMax / description

Previous value: -"End of a posting date range (YYYY-MM-DD)"New value: +"End of a posting date range (YYYY-MM-DD); use together with dateCreatedMin"

changedInput schema / properties / dateCreatedMin / description

Previous value: -"Start of a posting date range (YYYY-MM-DD)"New value: +"Start of a posting date range (YYYY-MM-DD); use together with dateCreatedMax"

changedInput schema / properties / skills / description

Previous value: -"Skill or keyword, e.g. \"python\""New value: +"Skill or keyword, e.g. \"python\"; same comma/+/- syntax as title"

changedInput schema / properties / title / description

Previous value: -"Free-text search in the job title, e.g. \"data engineer\""New value: +"Search in the job title. Comma = OR, prefix + = must contain, prefix - = exclude, quotes = exact phrase, e.g. \"data engineer\",-senior (exact phrase \"data engineer\", excluding senior)"

changedInput schema / properties / workPlace / description

Previous value: -"remote, hybrid, onsite, field or offshore"New value: +"remote, hybrid, onsite, field or offshore (use list_filter_values for all values)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "docs": {
+      "type": "string"
+    },
+    "url": {
+      "description": "RSS feed URL with a {YOUR_RAPIDAPI_KEY} placeholder",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "docs"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial context beyond the readOnly/openWorld annotations: it makes no API request, consumes no quota, returns a {YOUR_RAPIDAPI_KEY} placeholder the user must replace, and notes the free plan limit of 300 postings per month. These are exactly the non-obvious traits an agent needs before calling it.

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?

Three tight sentences, front-loaded with what the tool produces, then the key operational facts, then the routing hint. No filler and nothing redundant with the schema.

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?

For a URL-builder that returns no data, the description covers the essential facts: no request/quota cost, the key placeholder requirement, and the sibling alternative. An output schema exists, so return-value explanation is unnecessary.

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?

Schema description coverage is 100% across 18 parameters, so the schema already documents every filter in detail. The description only says results 'matching the filters' without adding syntax or semantics beyond the schema, so the baseline 3 applies.

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 ('Build a URL'), the resource ('Techmap's RSS API'), and the exact artifact produced (an RSS 2.0 feed URL matching the filters). It explicitly contrasts itself with search_jobs, so an agent can distinguish it from siblings without opening a schema.

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?

Gives concrete when-to-use cases (importing jobs into job board software for backfill, or an RSS reader) and names the alternative explicitly: 'Use search_jobs instead to see postings in this conversation.' Both the use and the exclusion are stated.

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

Deploy Server