Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_eightfold_board

List a company's public Eightfold AI job board by tenant subdomain and hiring domain, using limit/offset paging plus query and location filters.

Instructions

List an Eightfold tenant's job board. Lists a company's public Eightfold AI job board, paged via limit/offset. tenant is the {tenant}.eightfold.ai subdomain from the careers URL; domain is the hiring organization's own domain (e.g. microsoft.com), also visible on the tenant's careers page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, default 10, max 10 (upstream caps results per page regardless of a larger value)
queryNoFree-text search
domainYesHiring organization domain
offsetNoPage offset, default 0
tenantYesEightfold tenant subdomain (careers URL)
locationNoFilter: location contains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.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 burden. It discloses that the board is public and paged via limit/offset, which is useful, but it omits auth requirements, rate limits, and any indication of what a page returns.

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 front-loaded sentences that lead with the action and then define the fiddly parameters. There is mild redundancy between "List an Eightfold tenant's job board" and "Lists a company's public Eightfold AI job board," but nothing is wasted 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 6-parameter list tool with no output schema or annotations, the description covers the action, the pagination model, and the two non-obvious required parameters well. Return shape and auth remain unstated, but the core calling information is present.

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, but the description goes beyond the terse schema text by clarifying that tenant is the {tenant}.eightfold.ai careers subdomain and domain is the hiring org's own domain with the concrete microsoft.com example.

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 clear verb+resource ("List an Eightfold tenant's job board") and distinguishes itself from the sibling jobs_eightfold_job by scope (whole board vs. single posting). It never names a sibling explicitly, so differentiation is inferable rather than stated, keeping it below 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 Guidelines3/5

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

The description explains what tenant and domain mean and where to find them (careers URL, careers page), which helps correct invocation, but it gives no explicit when-to-use/when-not guidance or named alternative for the board-vs-job choice.

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