CareerProAI

careerpro_refresh

Reads each watched employer board's own public ATS feed (Greenhouse, Lever, Ashby, Workable) and files new matches. An account that watches no boards yet is first given the top 20 registry boards for its target titles (a shared registry of employers' public feeds; LinkedIn, Indeed and similar sites are never used). Returns seeded, fetched, matched, new and packs_built. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://careerpro.tech/pricing.json"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "careerpro_refresh"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive operation, and the description adds real context beyond them: it files new matches, it auto-seeds 20 registry boards for brand-new accounts (a non-obvious side effect), it never touches LinkedIn/Indeed, and it publishes a free quota of 200 calls/day per IP. What it does not clarify is what happens on repeated runs against already-seen postings, which matters for a non-idempotent tool.

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?

Three compact sentences with the core action front-loaded, followed by the seeding edge case and the return fields. The embedded pricing JSON is slightly clunky prose-wise but carries the quota information an agent needs, so little is wasted.

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 parameters and no output schema, the description does the heavy lifting well by enumerating the five returned fields (seeded, fetched, matched, new, packs_built) and the quota limit. The only gap is dedupe/repeat-run semantics for a non-idempotent refresh, which would matter for an agent planning successive calls.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is an empty object, so no compensation is needed.

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?

The description states a concrete verb and resource: it reads watched employers' public ATS feeds (Greenhouse, Lever, Ashby, Workable) and files new matches. That is far more specific than the tool name alone and clearly separates it from sibling read tools like careerpro_jobs_list or careerpro_pack_get. It stops short of explicitly naming an alternative, so it lands at 4 rather than 5.

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 rather than stated: an agent can infer this is the refresh/ingest step, and the description usefully notes the seeding path for accounts that watch no boards. However, there is no explicit 'call this when…' versus 'do not call this when…', and no guidance on how often to refresh despite the 200/day quota mention.

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

All CareerProAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?