Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_recruitee_offers

List a company's public Recruitee job offers with inline details; filter by department, location, or remote status via its careers subdomain.

Instructions

List a company's Recruitee offers. Lists a company's public Recruitee offers (detail is inline), optionally filtered by department, location, or remote. The company is the Recruitee subdomain from its careers URL https://{company}.recruitee.com/.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that offers are 'public' and that detail is inline, which is useful context, but says nothing about authentication, pagination, rate limits, or return shape for a listing operation.

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 action. The first two sentences overlap ('List a company's Recruitee offers' / 'Lists a company's public Recruitee offers'), a minor redundancy, but the filter and company-format details are efficient.

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?

For a read-only list tool with no annotations and no output schema, the description covers the resource, the filterable dimensions, and the required company identifier format. Pagination and response shape are unaddressed but are secondary for this kind of endpoint.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all four parameters. The description restates the department/location/remote filters and adds that company is the careers-URL subdomain, but this largely duplicates the schema's own wording rather than adding new semantics.

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 (company's Recruitee offers) with scope (public, per-company). It distinguishes itself implicitly from the singular jobs_recruitee_offer sibling by being the plural list and noting 'detail is inline', though it doesn't name the sibling explicitly.

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

Usage Guidelines3/5

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

The purpose implies when to use it (to enumerate a company's open roles), but there is no explicit when/when-not guidance or named alternative such as jobs_recruitee_offer for single-offer detail. Usage is left to inference.

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