Job Application Agent MCP Server

search_jobs

Read-only

Search current German job vacancies by role, city, and seniority level, returning short ranked listings with IDs for matching against a CV.

Instructions

Search current job vacancies in Germany (Arbeitnow job board).

    Args:
        query: What the job is about, e.g. "machine learning" or "data engineer".
            Do not put seniority or city here.
        location: City, e.g. "Berlin". Remote jobs match any location.
        level: Ranks this seniority higher: student, intern, entry or experienced.
        limit: Maximum number of results, 1-20.

    Returns short vacancies, best first. Use their `id` with score_match.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_jobs"
  }
}

Input Schema

Name	Required	Description	Default
`level`	No
`limit`	No
`query`	Yes
`location`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral context beyond that: results are 'short vacancies, best first', limit is bounded 1-20, and level acts as a ranking boost rather than a filter — a non-obvious trait an agent would otherwise guess wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then organized per-parameter in an Args block where every line adds actionable detail. Slightly docstring-flavored rather than prose, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description needn't enumerate return fields; it still notes the ordering and brevity of results, which aids interpretation. Combined with full parameter semantics and existing annotations, an agent has enough to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so well: it explains the semantic intent of each parameter, gives examples for query and location, states the 1-20 bound for limit, and clarifies that level ranks results rather than restricting them. This is meaning the schema alone cannot convey.

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 and resource ('Search current job vacancies') with a clear scope ('Germany (Arbeitnow job board)'), which an agent can immediately distinguish from siblings like score_match and read_cv. The parenthetical source name adds precision about what corpus is being searched.

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?

Gives concrete usage rules: what belongs in query vs. location ('Do not put seniority or city here'), and notes remote jobs match any location. It also routes downstream work to a sibling ('Use their `id` with score_match'), though it doesn't explicitly state when to prefer this tool over the other siblings.

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

Deploy Server