Skip to main content
Glama
mcp-public-intel

mcp-public-intel

by pecopeko

ats_company_jobs

Fetch normalized live job openings from public Greenhouse, Lever, and Ashby job boards, with remote/hybrid classification, salary, seniority, and tech-stack tags; no API key required.

Instructions

Fetch normalized live job openings from official public Greenhouse, Lever, or Ashby JSON job board APIs with remote/hybrid classification, salary extraction, seniority, and tech stack tags. Zero API key required.

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": {
      "provider": "<provider>",
      "company_slug": "<company_slug>"
    },
    "name": "ats_company_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return (1-100, default 25).
keywordNoOptional case-insensitive filter across title, department, location, tech tags, and description.
providerYesPublic ATS provider ('greenhouse', 'lever', or 'ashby').
remote_onlyNoIf true, return only roles classified as remote.
company_slugYesCompany job board slug (e.g. 'anthropic', 'stripe', 'openai', 'linear').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 load and does well: it discloses that results are normalized, that remote/hybrid classification and salary/seniority/tech-stack tags are derived, and that no authentication is needed. It stops short of rate limits, pagination behavior across providers, or what happens when an unknown slug or provider is supplied.

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 dense sentences, front-loaded with the core action and source, followed by the enrichment list and the zero-key reassurance. No filler and nothing that could be cut without losing 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?

For a five-parameter read tool with no output schema and no annotations, the description covers what is fetched, from where, and what derived fields come back. Only failure modes and per-provider pagination caveats are unaddressed, which is a minor gap.

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 all five parameters are already documented, including the provider enum and limit bounds. The description's mention of remote/hybrid classification lightly reinforces remote_only but adds no syntax or format detail beyond 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?

Names a specific verb and resource (fetch live job openings) plus the exact data source scope (Greenhouse, Lever, Ashby public JSON job board APIs) and the enrichment applied (remote/hybrid, salary, seniority, tech stack). This is unmistakably distinct from the SEC, podcast, Shopify and Substack siblings.

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 'Zero API key required' line tells the agent this works out of the box, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for simpler or non-ATS job lookups. Usage is only implied by the provider enumeration.

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