jobs
Server Details
Job search engine with 500k+ listings across Austria, Germany and Switzerland (alleskralle.com).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: search_jobs for listing job ads and fetch_job for retrieving full details. No overlapping functionality.
Both tool names follow a consistent verb_noun pattern (search_jobs, fetch_job), making them predictable and easy to understand.
With only two tools, the server feels minimal. While it covers the basic search and detail retrieval workflow, more tools (e.g., filtering, category listing) would better match the scope of a job search service.
The tools provide search and detail retrieval, covering the essential read operations. However, missing filters (e.g., by location, date) and lack of broader job exploration features leave some gaps for a comprehensive job search experience.
Available Tools
2 toolsfetch_jobAInspect
Liefert die vollständigen Details zu einer Stellenanzeige anhand ihrer id (aus search_jobs). Das Feld apply_url ist der Bewerbungslink zur Original-Anzeige. WICHTIG: apply_url NICHT selbst aufrufen oder abrufen — gib den Link dem Nutzer als anklickbaren Link aus, damit er sich bei Interesse selbst bewirbt bzw. die vollständige Anzeige öffnet.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Die id eines Treffers aus search_jobs. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the full burden. It discloses that apply_url is a link to the original posting and warns against fetching it. This adds behavioral context beyond the schema, though it could mention that it is a read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two concise sentences with a clear warning in caps. Every sentence adds value, and there is no redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description sufficiently explains what the tool returns (full details, apply_url) and the critical behavior regarding apply_url. It is complete enough for the intended use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already describes the id parameter as 'Die id eines Treffers aus search_jobs.' The description echoes this but does not add new parameter-specific meaning beyond reinforcing the origin.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool fetches complete details of a job posting by its id from search_jobs. It specifies the verb (liefert), resource (Details einer Stellenanzeige), and distinguishes from the sibling search_jobs which is for searching.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description indicates to use the id from search_jobs and gives an explicit instruction about not calling apply_url but presenting it as a clickable link. It implies usage after search_jobs, but does not explicitly state when not to use or provide alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_jobsAInspect
Sucht Stellenanzeigen auf alleskralle.com (DE/AT/CH) und liefert eine kompakte Liste (id, title, company, location, date). Die Bewerbungs-/Detail-URL ist NICHT in der Liste enthalten — für vollständige Details und den klickbaren Link rufe fetch_job mit der id auf. Hinweis: "remote" ist eine Volltext-Heuristik (kein strukturiertes Feld), kann also ungenau sein. Blättern nur über das zurückgegebene next_cursor möglich; die Seitenzahl ist begrenzt.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Suchbegriff (Jobtitel, Tätigkeit, Skill). | |
| cursor | No | next_cursor aus einer vorherigen Antwort, um die nächste Seite zu laden. | |
| remote | No | Auf Remote-/Homeoffice-Stellen einschränken (Heuristik). | |
| country | No | Strikt auf ein Land einschränken: AT (Österreich), DE (Deutschland) oder CH (Schweiz). Kombinierbar mit location. | |
| location | No | Ort, Stadt oder PLZ. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that remote is a full-text heuristic (not structured), pagination only via cursor, and that the page limit exists. It does not mention rate limits or authentication, but the provided information is adequate for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, dense paragraph that efficiently conveys purpose and key details. It front-loads the main action. Minor improvement could be structured with bullet points, but it is concise and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description sufficiently explains what is returned (compact list with fields) and what is missing (detail URL). It also covers pagination and page limit, making it complete for a search tool without over-specifying.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds value by explaining the heuristic nature of 'remote', the pagination mechanism for 'cursor', and that 'country' is strict and combinable with location. This goes beyond mere schema repetition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches job listings on alleskralle.com (DE/AT/CH) and returns a compact list of fields (id, title, company, location, date). It distinguishes from sibling tool fetch_job by noting that the detail URL is not included in this response.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly guides usage by stating that for full details and clickable links, one should call fetch_job with the id. It also provides context about remote being a heuristic and pagination via next_cursor. However, it does not explicitly state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!