Skip to main content
Glama

search_jobs

Filter the agenticjobs.dev index by free-text and structured constraints. Returns up to limit rows sorted by vibe-coding fit, each description cut to 240 characters. The strongest single tool — call this first.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree-text — matches title, company, tags, AI-tool names.
idsNoNarrow to these postings — pass ids from an earlier answer to re-check them under new conditions.
limitNo
toolsNoRestrict to jobs mentioning these AI-coding tools (e.g. Claude Code, Cursor, Codex).
sourceNo
countryNoFull country names (Germany, UK, USA), not ISO codes.
min_scoreNoMinimum LLM rubric score: 70 is a good fit, 85 the curated top.
exclude_idsNoDrop these postings — pass ids the person has already been shown.
remote_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose non-obvious behavior: result count is capped by `limit`, rows are sorted by 'vibe-coding fit', and each description is truncated to 240 characters. Missing are auth/rate-limit context, whether a total match count is returned, and any pagination or offset behavior — meaningful gaps for a 9-parameter search.

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?

Three short sentences, front-loaded with the core action, then return shape, then routing advice. No filler and no restatement of the tool name; the self-referential 'strongest single tool' line still earns its place as a routing cue.

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 9-parameter, zero-required search tool with no output schema and no annotations, the description does the important compensating work: it explains the result shape, ordering, and truncation. It is not fully complete — no result-set size/emptiness behavior and no guidance on combining filters — but the essentials are present.

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 67%, so the schema already documents most parameters, including the intent of `ids`, `exclude_ids`, `min_score`, and `country`. The description only adds meaning to `limit` (row cap) and the implicit sort key behind `min_score`/vibe fit; it says nothing extra about `q`, `tools`, `source`, or `remote_type`.

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 a specific verb and resource: 'Filter the agenticjobs.dev index by free-text and structured constraints.' The scope (free-text + structured filters) is precise enough to distinguish it from a single-record lookup like get_job, but no sibling is named, so the agent must infer differentiation from titles alone.

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?

'The strongest single tool — call this first' gives a clear entry-point routing rule, which is real when-to-use guidance. It stops short of explicit exclusions (when to use fetch_jobs, get_job, or vibe_top instead), so the agent has a default but no negative guidance.

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