Conecto

List applicants

hiring_list_applicants

Read-onlyIdempotent

Applicants, newest first or by match score: for one job or all, at one stage, matching a name or email, by risk, or the ones kept as spam. Free.

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

Input Schema

Name	Required	Description	Default
`job`	No	The job (its slug from hiring_list_jobs).
`risk`	No	Only applications whose checks found high risk, minor signals, or none.
`sort`	No	match: the highest match score first, the unscreened last.	newest
`spam`	No	true: only applications kept as spam (from the blocklist, or marked).
`limit`	No
`match`	No
`query`	No
`stage`	No
`offset`	No
`screened`	No	true: only screened ones; false: only those not yet.
`min_match`	No	Only screened applications whose match score is at least this.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description adds a genuinely new fact: the call is 'Free' (no credit consumption). Beyond that it says nothing about result size, pagination behaviour, or default limits, which matter for an 11-parameter listing call.

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?

A single dense sentence with the resource and the default ordering front-loaded, then the filter axes. Zero boilerplate or repetition of schema detail.

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?

With 11 optional parameters and no output schema, the description should clarify what a result row contains and how paging (limit/offset, max 200) behaves. It covers the filter surface reasonably but leaves the return shape entirely to inference.

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 55%, so the schema carries part of the load. The description does add real meaning the schema lacks, notably that query matches against name or email, and it groups the filter dimensions into readable prose. But it omits several documented gaps (match strength, min_match, screened), so it compensates only partially.

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 names the resource (applicants) and enumerates the filter axes it exposes, so an agent knows it is a filtered retrieval over applicants with a defined default order (newest first). It never distinguishes itself from nearby siblings such as hiring_screen_queue or hiring_get_applicant, which keeps it short of 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 only implied by the enumeration of filter options (one job or all, one stage, spam or not). There is no explicit statement of when to reach for this versus hiring_screen_queue for a work queue or hiring_get_applicant for a single record, and no exclusions are given.

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

All Conecto 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?