Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Find matching candidates

find_candidates
Read-onlyIdempotent

AI talent search over opted-in candidate profiles for a job (jobId) or a description/skills. Plan-gated (candidate matching); if the plan lacks it the result says which upgrade is needed.

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_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNoJobiba job ID (the id field from search_jobs or list_my_jobs).
limitNoMax 25.
titleNoRole title if no jobId.
locationNoOptional.
minScoreNo0-100 minimum match score.
remoteTypeNoOptional.
descriptionNoRole description if no jobId.
requiredSkillsNoMust-have skills.
experienceLevelNoOptional.

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the feature is plan-gated and a failed call returns which upgrade is needed, and results are limited to opted-in profiles.

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 sentences, front-loaded with the core purpose and then the gating condition. No filler or repeated phrasing.

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 read-only, idempotent search with a fully described schema, the definition covers purpose, input modes, and the plan-gating failure mode. It does not mention result shape or ordering, but without an output schema that gap is minor for a search tool bounded by a documented limit.

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 description coverage is 100%, so the nine parameters are already documented individually, and the schema itself notes the jobId-vs-description alternatives. The description restates that either a jobId or a description/skills drives the search but adds no format or interplay detail beyond the schema, so the baseline 3 applies.

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: 'AI talent search over opted-in candidate profiles', plus the two input modes (jobId or description/skills). It does not explicitly distinguish itself from nearby siblings such as screen_applicants or list_shortlist, so a 4 rather than a 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 by the two input modes ('for a job (jobId) or a description/skills'), which tells an agent how to invoke it but not when to pick it over applicant-listing or shortlist tools. No exclusions or prerequisites beyond the plan gate are given.

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.