Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_smartrecruiters_posting

Retrieve a single SmartRecruiters posting by company and posting ID, returning title, location, employment type, URLs, compensation, and ad text without recruiter personal data.

Instructions

Get a single SmartRecruiters posting. Returns one SmartRecruiters posting, identified by the company id and posting id, both required. The response has the title, department, location, employment type, posting and apply URLs, posting date, compensation, and the job ad description as HTML and text. Recruiter personal data is left out. An unknown company or id returns 404.

Input 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?

With no annotations, the description carries the full burden and delivers well: it enumerates the returned fields, discloses that recruiter personal data is excluded, and documents that an unknown company or id returns a 404. It stops short of stating auth requirements or rate limits, but for a read-only getter this is solid disclosure.

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?

Four sentences, front-loaded with the action and identifiers, followed by return contents, privacy note, and error behavior. Each sentence adds something, though the return-field enumeration is dense and could be tightened.

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 and no annotations, the description compensates by describing the response shape, the privacy exclusion, and the 404 failure mode. An agent has enough to call it correctly; only auth/permission prerequisites are 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 both parameters are already documented in the schema. The description adds only the confirmation that both are required and what they identify, which is marginal but consistent with the baseline when the schema does the heavy lifting.

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?

States a specific verb ('Get') and resource ('a single SmartRecruiters posting'), and the word 'single' implicitly contrasts with the sibling jobs_smartrecruiters_postings list tool. An agent can distinguish the detail-fetch from the list without opening either schema.

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 implies usage by requiring both company and posting id and calling it a 'single' posting, but it never states when to use this versus the listings sibling or names any alternative. Usage context is inferable rather than explicit.

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