Skip to main content
Glama

Arbeitnow

by io.github.pipeworx-io

List Jobs

list_jobs
Read-onlyIdempotent

List recent job postings from Arbeitnow, a keyless European (Germany-heavy) job board with many English-speaking and visa-sponsorship roles. Returns one page of postings in reverse-chronological order (newest first). HTML descriptions are omitted from this list — use get_job for the full description. Use page to paginate and remote_only to keep only remote jobs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1). 100 jobs per page.
remote_onlyNoIf true, keep only jobs where remote is true (default false).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive properties. The description adds behavioral context such as reverse-chronological ordering, one-page results, and omission of HTML descriptions. No contradictions with 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?

Three well-structured sentences. The first sentence provides purpose and context, the second explains ordering and exclusion, and the third tells how to use parameters. No unnecessary words.

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?

Given the tool's simplicity (2 optional params, no output schema, full annotations), the description covers all necessary aspects: data source, ordering, filtering, pagination, and relation to sibling. It is complete for an AI agent to use correctly.

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% with descriptions and examples. The description reinforces usage of 'page' and 'remote_only', adding that page defaults to 1 with 100 jobs per page and remote_only filters to remote jobs. This adds value beyond the schema.

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 identifies the tool as listing recent job postings from Arbeitnow, specifying the board's characteristics (European, Germany-heavy, English-speaking, visa-sponsorship). It also distinguishes from the sibling get_job by noting that HTML descriptions are omitted.

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 explains when to use the tool (to list jobs, paginate, filter remote) and references get_job as an alternative for full descriptions. However, it does not explicitly mention when not to use it, though the context is clear enough.

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

All Arbeitnow 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

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, from job searching to company research to bet analysis. Even closely related tools like ask_pipeworx and ask_pipeworx_grounded are differentiated by one being hallucination-resistant. Memory and subscription tools are clearly separated.

Naming Consistency4/5

Most tools follow a verb_noun pattern (e.g., search_jobs, validate_claim, subscribe). However, some tools like pipeworx_feedback, pipeworx_trending, entity_profile deviate with noun_noun or proper noun patterns, creating minor inconsistency.

Tool Count4/5

29 tools is above the typical 3-15 range, but the server covers a wide breadth of domains (jobs, company data, betting, memory, monitoring) so each tool earns its place. Slightly over-scoped but reasonable.

Completeness3/5

The tool set covers many domains but has notable gaps. For jobs, only search/list/get exist (no create/update/delete). For company data, update is missing. For betting, there is analysis but no placement. The set is broad but not deeply complete for any single domain.

Resources