Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_workable_postings

Retrieve a company's public Workable job postings in a structured format, with optional filters for department, location, remote status, and free-text search.

Instructions

List a company's Workable postings. Lists a company's public Workable postings in the shared Job shape, optionally filtered by department, location, or remote. The company is the Workable account slug from its careers URL https://apply.workable.com/{company}/. Detail (full description) is fetched per job via the single-posting endpoint.

Input Schema

NameRequiredDescriptionDefault
remoteNoFilter by remote (true or false)
searchNoFree-text search
companyYesWorkable account slug (careers URL)
locationNoFilter: location contains
departmentNoFilter: department contains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description still discloses key behavioral facts: the postings are public, they are returned in the shared Job shape, and full descriptions are not included here but must be fetched via the single-posting endpoint. It does not cover pagination or authentication requirements, but for a public read-only list tool the disclosed scope is meaningful.

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?

The description is front-loaded and efficient, moving from purpose to filters to company identification to the detail-workflow note. There is slight redundancy between the first and second sentences, but no wasted content overall.

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 list tool with no output schema, the description is fairly complete: it identifies the result shape, filtering options, required company slug, and the alternative endpoint for full details. It lacks pagination or result-limit guidance and does not mention the search parameter, but nothing critical for calling it correctly is missing.

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 five parameters. The description confirms filtering by department, location, and remote and explains the company slug, but it adds little beyond the schema and it omits the search parameter from its filter list.

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 states a specific verb and resource: 'List a company's Workable postings.' It distinguishes this tool from the single-posting endpoint by explaining that detail is fetched per job via the single-posting endpoint.

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 makes clear this is a listing tool and names the single-posting endpoint for retrieving full descriptions, giving clear context for when to use each. It does not explicitly state when-not to use it or name other ATS list alternatives, but the provider is obvious from the tool name.

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