Skip to main content
Glama

careerpro_jobs_list

Read-onlyIdempotent

Openings gathered from the employer boards you watch, ranked by keyword fit, with the screen verdict for each. Key from careerpro.tech/auto-apply. Scope read. 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_jobs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit
stageNostage
verdictNoverdict

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real context beyond them: results are ranked by keyword fit, each carries a screen verdict, and keying is required from a specific URL. The embedded pricing block also discloses a rate ceiling of 200 calls/day per IP, which matters for an agent planning repeated polling. It omits pagination behavior despite a limit parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded and earns its place by describing ranking and the per-row verdict. The remainder is cluttered by a raw pricing JSON blob and the fragment 'Scope read', which read like injected boilerplate rather than prose an agent can parse quickly.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with no output schema, the description does convey the shape of the response (ranked openings with a verdict each) and the auth requirement. It leaves gaps that matter in practice: no pagination semantics for limit, no enumeration of stage/verdict values, and no indication of default ordering when no keyword match applies.

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 nominally 100%, but the schema 'descriptions' are bare restatements of the parameter names ('limit', 'stage', 'verdict'), so they carry almost no meaning. The description hints that 'verdict' relates to the screen verdict and that results are ranked, but never explains what values 'stage' or 'verdict' accept or how filtering interacts with ranking. Baseline 3 is the right ceiling here.

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?

States the resource precisely — job openings from watched employer boards — and adds the ordering rule (keyword fit) plus what accompanies each row (screen verdict). An agent knows this is a read/list endpoint. It stops short of naming which sibling to use instead when the agent wants refresh or submission data.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance relative to siblings such as careerpro_refresh or careerpro_ats_score. The only routing hint is an authentication pointer ('Key from careerpro.tech/auto-apply') and a terse 'Scope read' fragment, which tells the agent how to authenticate, not when this tool is the right choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources