Comeet MCP Server and API by Cotlet

List candidates in Comeet

comeet_list_candidates

Read-onlyIdempotent

List candidates in the user's own Comeet account from ChatGPT, Claude or any AI agent. Returns how to do it in Comeet step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Comeet Cloud Browser. Comeet's official API: Comeet, now Spark Hire Recruit, has a Recruiting API, but Comeet grants access at its sole discretion under partner terms (checked 22 Oct 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds the crucial behavioral detail that it 'opens nothing by itself' and returns step-by-step instructions (screens, buttons, fields). It also notes that Comeet API access is discretionary, giving useful context for agent decision-making.

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 content is reasonably sized but not optimally front-loaded; the first sentence suggests a listing action before clarifying the instructional nature. The API sentence adds context but dilutes focus. It could be more direct by stating 'Returns step-by-step instructions for listing candidates' upfront.

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?

Given the tool has no parameters, no output schema, and annotations covering safety, the description provides sufficient context: it explains that it returns instructions and does not open anything, and directs the agent to use browser tools afterward. The API access note adds extra context, though the output format of the instructions is not detailed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline score of 4 applies. The description adds no parameter details but none are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'List candidates' but then clarifies that the tool returns step-by-step instructions and opens nothing by itself, revealing a guide/instruction tool rather than a data-listing tool. The core purpose is stated but the initial phrasing is misleading about what the tool actually does.

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 implies the tool should be used first, then followed by cotlet_browser_* tools, but does not explicitly say when to use this versus navigating directly or using other Comeet tools. The API access note provides context on why not to use the official API, but no explicit 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 Comeet MCP Server and API by Cotlet 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?