Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_icims_job

Retrieve a single iCIMS job posting by domain and req_id/slug to get its HTML/text description, department, and benefits.

Instructions

Get a single iCIMS job. Returns a single iCIMS job with its full HTML/text description, department, and benefits. id is the req_id/slug from a board listing; lang defaults to en-us.

Input Schema

NameRequiredDescriptionDefault
idYesiCIMS job req_id/slug from a board listing
langNoLanguage code, default en-us
domainYesiCIMS tenant careers domain

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 behavioral burden. 'Get' plus the stated return fields (full HTML/text description, department, benefits) correctly signals a read operation and discloses the payload, but there is no mention of auth requirements, rate limits, or error behavior for a missing/invalid req_id.

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 tight sentences with zero filler, front-loaded with the action and the return payload before the parameter notes. Every clause earns its place.

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?

With no output schema, the description steps in to summarize the returned fields, which is the key information an agent needs. It is nearly complete for a read-only detail tool, with only the domain parameter and failure modes left unaddressed.

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 coverage is 100%, so the schema already documents all three parameters; baseline is 3. The description adds only marginal value, clarifying that id is a req_id/slug from a board listing and that lang defaults to en-us — both of which are already in the schema descriptions — while the domain parameter is not addressed at all.

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 iCIMS job') and describes what the response contains (HTML/text description, department, benefits). It implicitly differentiates from the board-listing sibling by noting the id comes 'from a board listing', but never names jobs_icims_board explicitly, so the sibling contrast is inferential rather than stated.

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?

There is no explicit when-to-use/when-not-to-use guidance or named alternative. The clue that 'id is the req_id/slug from a board listing' implies the tool should be called after retrieving a listing, which is useful implied usage, but it never spells out the workflow or prerequisites.

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