Skip to main content
Glama

stellenonline.de Jobsuche

Search jobs

search_jobs
Read-onlyIdempotent

Search for jobs in the STON job database. Returns structured JSON.

Call this tool ONCE per user request, then present the returned jobs list to the user in whatever format fits (markdown list, table, plain text). Always include the apply link from the url field for each job. If has_more is true, mention total_found and ask whether to fetch more. NEVER call this tool multiple times in a row to collect all pages automatically.

To count results without fetching full job data, prefer count_jobs. If a filter you need isn't on count_jobs, call this tool with rows=1 and read total_found (the count is server-side and independent of rows).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch keywords (German job market — examples: "Softwareentwickler Python", "Krankenpfleger")
pageNoPage number starting at 1
rowsNoResults per page, 1-50 (default: 25)
sortNo"relevance" (default) or "date" (newest first)
radiusNoSearch radius in km around the location, e.g. 25, 50 (default: server setting)
locationNoCity, region or area, e.g. "München", "Ravensburg", "Bodensee", "Baden-Württemberg"
has_salaryNoIf True, return only jobs that advertise a salary at all (any amount); if False, only jobs without one. Leave unset to ignore.
max_salaryNoMaximum annual gross salary in EUR (optional, same overlap semantics)
min_salaryNoMinimum ANNUAL gross salary in EUR (optional), e.g. 60000. Filtered server-side. Jobs advertised per month/hour are normalised to a yearly figure first, so e.g. 5000/month matches min_salary=60000. Salary ranges match on OVERLAP, not containment: a job advertised as 30.000–45.000 € IS returned at min_salary=40000 (the ranges overlap), and is NOT returned at max_salary=25000.
working_planNoOne of: "Vollzeit", "Teilzeit", "Minijob", "Homeoffice" (comma-separated for multiple)
job_offer_typeNoOne of: "Arbeitsplatz", "Ausbildung", "Praktikum", "Freiberuflich", "Werkstudent", "Trainee", "Duales-Studium" (comma-separated for multiple)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / has_salary / description
      Added value: +"If True, return only jobs that advertise a salary at all\n        (any amount); if False, only jobs without one. Leave unset to ignore."
    • addedInput schema / properties / job_offer_type / description
      Added value: +"One of: \"Arbeitsplatz\", \"Ausbildung\", \"Praktikum\", \"Freiberuflich\", \"Werkstudent\", \"Trainee\", \"Duales-Studium\" (comma-separated for multiple)"
    • addedInput schema / properties / location / description
      Added value: +"City, region or area, e.g. \"München\", \"Ravensburg\", \"Bodensee\", \"Baden-Württemberg\""
    • addedInput schema / properties / max_salary / description
      Added value: +"Maximum annual gross salary in EUR (optional, same overlap semantics)"
    • addedInput schema / properties / min_salary / description
      Added value: +"Minimum ANNUAL gross salary in EUR (optional), e.g. 60000.\n        Filtered server-side. Jobs advertised per month/hour are\n        normalised to a yearly figure first, so e.g. 5000/month matches\n        min_salary=60000. Salary ranges match on OVERLAP, not containment:\n        a job advertised as 30.000–45.000 € IS returned at min_salary=40000\n        (the ranges overlap), and is NOT returned at max_salary=25000."
    • addedInput schema / properties / page / description
      Added value: +"Page number starting at 1"
    • addedInput schema / properties / q / description
      Added value: +"Search keywords (German job market — examples: \"Softwareentwickler Python\", \"Krankenpfleger\")"
    • addedInput schema / properties / radius / description
      Added value: +"Search radius in km around the location, e.g. 25, 50 (default: server setting)"
    • addedInput schema / properties / rows / description
      Added value: +"Results per page, 1-50 (default: 25)"
    • addedInput schema / properties / sort / description
      Added value: +"\"relevance\" (default) or \"date\" (newest first)"
    • addedInput schema / properties / working_plan / description
      Added value: +"One of: \"Vollzeit\", \"Teilzeit\", \"Minijob\", \"Homeoffice\" (comma-separated for multiple)"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely new behavior: the tool returns a `jobs` list with `url`, `has_more` and `total_found`, and the count is server-side and independent of `rows`. It does not restate annotation claims, though some narration of return fields overlaps the existing output schema.

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 purpose and the one-call rule, then the count/pagination guidance. Slightly padded by presentation instructions ("markdown list, table, plain text") that matter less for tool selection, but nothing is buried or redundant.

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?

Eleven optional parameters are all described in the schema, an output schema exists, and annotations cover safety, so the description only needs to add workflow and pagination policy — which it does completely, including the total_found trick for unsupported filters.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds a non-obvious usage of `rows` (set rows=1 to read `total_found` as a cheap count) that an agent would not derive from the schema alone. It does not re-explain salary overlap or enum values, which the schema already handles.

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?

Opens with a specific verb+resource ("Search for jobs in the STON job database") and immediately distinguishes itself from the counting sibling by naming `count_jobs` and describing the rows=1 fallback. An agent can tell search from count 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?

Explicit when-to-use rules: call once per request, never loop to collect pages, and route pure-counting requests to `count_jobs` or to this tool with rows=1. Exclusions ("NEVER call this tool multiple times in a row") are stated as clearly as the positive cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources