Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

jobs_rippling_board

List a company's public Rippling job postings by board slug, including title, department, and work location, with filters for remote, location, and department.

Instructions

List a company's Rippling job board. Lists a company's public Rippling board postings (thin listing — title, department, work location). The company is the Rippling board slug from its careers URL https://ats.rippling.com/{company}/jobs. Detail (full description, employment type) is fetched per job via the single-job endpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "jobs_rippling_board"
  }
}

Input Schema

Name	Required	Description
`remote`	No	Filter by remote (true or false)
`company`	Yes	Rippling board slug (careers URL)
`location`	No	Filter: location contains
`department`	No	Filter: department contains

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Jul 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return shape ('thin listing — title, department, work location'), which prevents an agent from expecting full job descriptions. It does not mention pagination, rate limits, or auth, but for a read-only listing tool the key behavioral trait (what you actually get back) is covered.

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?

Front-loaded with the core action and scoping, but the first two sentences restate each other ('List a company's Rippling job board' vs 'Lists a company's public Rippling board postings'), a small redundancy that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies exactly what is missing: the return shape of the listing, the slug source URL, and where detail lives. Nothing essential for correctly calling this listing tool is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful value by giving the concrete careers-URL template (https://ats.rippling.com/{company}/jobs) that defines the required 'company' slug, beyond the schema's brief 'Rippling board slug (careers URL)' text. The filter parameters (remote, location, department) are left entirely to the schema.

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 ('List') and resource ('a company's Rippling job board'), clarifies it returns public postings, and explicitly distinguishes itself from the single-job endpoint used for detail. An agent can tell this apart from the numerous other job-board siblings and from jobs_rippling_job without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly routes the agent: use this for the thin listing, and fetch full description/employment type via the single-job endpoint. This names the alternative and the condition selecting it, though it lacks an explicit when-not or a statement of prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server