Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_teamtailor_jobs

List a company's public Teamtailor job board and return job details, with optional filters for department, location, and remote roles.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.9/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 does disclose that the feed is public and returns the shared Job shape with detail inline, which is useful. However, it omits rate limits, pagination, and any note on failure modes when the subdomain is invalid, so it is only partially transparent.

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 primary action, with the URL-format detail placed last where it is needed. No wasted prose, though the opening sentence and second sentence overlap somewhat in restating the board feed.

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 supplies the required company input semantics, the filter options, and the return shape. It is nearly complete; only pagination/rate-limit behavior is unaddressed, which is minor for this tool class.

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% (baseline 3), and the description goes beyond it by explaining that `company` is the subdomain extracted from the careers URL https://{company}.teamtailor.com/, which is genuinely useful for constructing the value. The filter params are only restated, not elaborated, but the company hint lifts it above baseline.

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?

States a specific verb ('List') plus resource ('a company's Teamtailor job board') and identifies the source platform, which cleanly separates it from sibling board tools like jobs_greenhouse_board or jobs_lever_postings. An agent can tell what it returns (public board feed in the shared Job shape) without opening the schema.

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 description implies usage ('optionally filtered by department, location, or remote') but never states when to choose this over the other job-board siblings, nor any prerequisite beyond knowing the company subdomain. Adequate context, no exclusions or alternatives named.

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