Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_personio_feed

Fetch a company's public Personio job board as structured listings with inline details, optionally filtered by department, location, or remote status.

Instructions

List a company's Personio job board. Lists a company's public Personio board feed in the shared Job shape with detail inline, optionally filtered by department, location, or remote. The company is the Personio subdomain from its careers URL https://{company}.jobs.personio.de/.

Input Schema

NameRequiredDescriptionDefault
remoteNoFilter by remote (true or false)
companyYesPersonio subdomain (careers URL)
locationNoFilter: location contains
departmentNoFilter: department contains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the feed is 'public' and that job 'detail' is included inline, which tells the agent no separate detail call is needed. However, it omits pagination behavior, rate limits, error handling, and any authentication caveats, leaving meaningful behavioral gaps.

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?

Three sentences, front-loaded with the tool's action. The first two sentences are slightly redundant ('List a company's Personio job board' vs 'Lists a company's public Personio board feed'), but the URL-pattern detail in the final sentence earns its place and the description stays compact.

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?

Given four parameters, no output schema, and no annotations, the description does a good job: it names the return shape ('shared Job shape with detail inline'), explains the company identifier derivation, and lists the optional filters. Only pagination and rate-limit behavior are missing, which keeps it from a 5.

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. The description adds real value by explaining how to derive the required 'company' value: the Personio subdomain from the careers URL pattern https://{company}.jobs.personio.de/. It also reinforces the department, location, and remote filters, though without adding syntax beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('a company's Personio job board'), and the second sentence clarifies it returns the public board feed in a shared Job shape. The provider name (Personio) implicitly distinguishes it from other job-board tools, but the description never explicitly contrasts with siblings like jobs_greenhouse_board or jobs_ashby_board, so it stops just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool returns and which filters exist, but gives no when-to-use guidance, no prerequisites, and no alternatives (e.g., jobs_company_search or other job-board feeds). An agent must infer the use case from the provider name alone.

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

Deploy Server

Other Tools