Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_smartrecruiters_posting

Fetch a single SmartRecruiters job posting by company and posting ID as credential-free public ATS JSON, including the jobAd description while omitting recruiter personal data.

Instructions

Get a single SmartRecruiters posting. Returns a single SmartRecruiters posting with its jobAd description. Recruiter personal data is intentionally omitted. Credential-free public ATS JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSmartRecruiters posting id
companyYesSmartRecruiters company id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior4/5

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

In the absence of annotations, the description discloses important behaviors: it omits recruiter personal data, is credential-free (public), and returns JSON. This provides good transparency beyond the schema, though could mention error behavior.

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?

The description is two sentences, clear and to the point with no wasted words. Could be slightly more structured, but effectively conveys the necessary information.

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?

Given no output schema or annotations, the description covers the return content (jobAd description, omitted recruiter data) and the public nature. It is complete enough for a simple retrieval tool, though an explicit output format note would be beneficial.

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% with descriptions for both `id` and `company`. The description does not add additional parameter-level meaning beyond what the schema provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves a single SmartRecruiters posting, including the jobAd description, and specifies that recruiter personal data is omitted. It distinguishes from the sibling tool `jobs_smartrecruiters_postings` which lists postings.

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 the tool retrieves a single posting, but does not explicitly provide when-to-use or alternatives like `jobs_smartrecruiters_postings` for listing. The mention of 'credential-free' is helpful but not a full usage guideline.

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