Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

jobs_ashby_board

List an organization's public Ashby job board postings by careers URL slug, including details and optional compensation.

Instructions

List an organization's Ashby job board. Lists an organization's public Ashby board postings with inline detail (description, compensation when include_compensation=true). The org is the Ashby slug from its careers URL. An unknown org returns an empty board (Ashby does not 404).

Input Schema

NameRequiredDescriptionDefault
orgYesAshby org slug (careers URL)
include_compensationNoInclude compensation summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.6/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 behavioral burden. It usefully discloses that postings come with inline detail and that an unknown org returns an empty board rather than a 404 — genuinely non-obvious behavior. However it says nothing about pagination, rate limits, or auth expectations implied by "public".

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 short sentences, front-loaded with the core action, and each one earns its place: the naming, the return content, the org-slug convention, and the empty-board edge case. No padding.

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 two-parameter list tool with no output schema and no annotations, the description covers the source, the org-slug convention, partial return contents, and the key edge case, which is largely sufficient. Missing only pagination/volume expectations for a full board listing.

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 both parameters, making 3 the baseline. The description adds a little framing (org as the slug from the careers URL; compensation appearing only when include_compensation=true) but nothing the schema does not already convey.

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?

The description gives a specific verb and resource ("List an organization's Ashby job board... public Ashby board postings") and specifies scope (public) plus returned content (inline description, compensation). The Ashby provider naming effectively separates it from the many other jobs_* board tools, though it never explicitly routes the agent against a named sibling.

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?

Usage is only implied: it is clear you use this when the org's board is Ashby-hosted, but there is no explicit when-to-use / when-not-to-use statement and no named alternative among the Greenhouse/Lever/Workday/Workable board siblings. Adequate but leaves the routing inference to the agent.

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