Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_smartrecruiters_postings

Fetch public SmartRecruiters job postings for a company by its careers URL identifier; use limit and offset to page results.

Instructions

List a company's SmartRecruiters postings. Lists a company's public SmartRecruiters postings, paged via limit/offset. The company is the SmartRecruiters identifier from its careers URL.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, default 100, max 100
offsetNoPage offset, default 0
companyYesSmartRecruiters company id (careers URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It usefully discloses that only 'public' postings are returned and that results are paged via limit/offset, but says nothing about read-only safety, rate limits, or failure modes.

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?

Two short, front-loaded sentences with no filler. Slight redundancy: the first sentence is essentially restated with the added 'public' qualifier in the second, which keeps it from a perfect score.

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 simple paginated list tool with no output schema and no annotations, the description covers scope (public postings), pagination, and the company identifier's origin. Adequate, though it does not describe the returned fields or ordering.

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 limit, offset, and company. The description's note that company is the identifier 'from its careers URL' largely restates the schema's own '(careers URL)' hint, adding little new meaning; baseline 3 applies.

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 (List) and resource (a company's SmartRecruiters postings), and the platform naming distinguishes it from the many other jobs_* siblings (greenhouse, workable, lever). It does not explicitly contrast with the near-named jobs_smartrecruiters_posting singular detail tool, leaving that distinction to inference.

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 implied by 'List a company's ... postings,' but there is no explicit when-to-use vs alternatives guidance and no exclusions (e.g., when to pick this over jobs_company_search or the single-posting sibling). Context is only indirectly provided.

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