Skip to main content
Glama

find_jobs

Read-onlyIdempotent

Find saved job candidates by normalized URL or company and title. Follow next_cursor; ask the user to resolve ambiguous matches.

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": "find_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
titleNo
cursorNo
companyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add behavioral context — and it does: pagination via next_cursor and the rule to stop and ask the user when matches are ambiguous. Those are non-obvious behaviors an agent would otherwise get wrong. What's missing is any hint about result shape or how many matches to expect.

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 short sentences, lookup keys first, behavioral rules second. No filler, no restatement of the tool name, and the most actionable instruction (follow next_cursor) is not buried.

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 four-optional-parameter read-only lookup with no output schema, this covers the essentials: how to search, how to paginate, and what to do on ambiguity. The remaining hole is the all-parameters-empty case, which is legal per the schema but 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 0%, so the description must carry the load and it partially does: it establishes that url OR (company AND title) are the two lookup modes, an ordering the schema's flat optional-fields list does not express. It also explains the cursor parameter's purpose. It leaves the 'normalized' URL format undefined and never mentions what an empty call returns, which are the details an agent most needs.

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 gives a specific verb plus resource ('Find saved job candidates') and the lookup keys it accepts, which is more than the bare name find_jobs conveys. It also implicitly separates itself from capture_job and get_job by specifying 'saved' records and a lookup-by-URL-or-company/title mode. Minor friction: the resource is called 'job candidates' while the tool and siblings talk about 'jobs', which could cause a moment of doubt.

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?

It states the conditions under which you'd call it (you have a normalized URL, or a company and title) and gives an explicit escalation rule: ask the user to resolve ambiguous matches. That is real when-to-use guidance. However, it never says what to do when no identifiers are available, nor does it name or exclude any sibling such as get_job or list_jobs_for_assessment.

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