Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_eightfold_job

Retrieve a single Eightfold job posting by tenant, domain, and position ID, returning its full HTML or text description for detailed job review.

Instructions

Get a single Eightfold position. Returns a single Eightfold position with its full HTML/text description. id is the position id from a board listing; tenant/domain as in the board endpoint.

Input Schema

NameRequiredDescriptionDefault
idYesEightfold position id from a board listing
domainYesHiring organization domain
tenantYesEightfold tenant subdomain

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?

No annotations are provided, so the description carries the burden alone. It does disclose the return payload ('full HTML/text description'), which is useful behavioral context, and 'Get' implies a read-only operation. However, it says nothing about auth requirements, rate limits, or error/not-found behavior.

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?

Two compact sentences with the purpose front-loaded, followed by the return payload and parameter provenance. No filler or redundancy.

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 detail tool with full parameter documentation and no output schema, the description covers purpose, return shape, and parameter origin, which is close to complete. It leaves auth and failure modes unspecified, but those are peripheral for this tool type.

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 baseline is 3. The description largely restates the schema for id/domain/tenant, adding only the relational hint that tenant/domain mirror the board endpoint, which is marginal value over the structured fields.

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 and resource: 'Get a single Eightfold position.' It distinguishes itself from listing-style siblings by emphasizing 'a single' and by tying the id to 'a board listing,' which implicitly points at jobs_eightfold_board. It stops short of naming the sibling outright.

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: the agent learns the id must come from a board listing and tenant/domain follow the board endpoint, which sketches a prerequisite flow. There is no explicit when-to-use or when-not-to-use guidance nor any named alternative.

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