Recruiterflow MCP Server and API by Cotlet

Create task in Recruiterflow

recruiterflow_create_task

Read-onlyIdempotent

Create task in the user's own Recruiterflow account from ChatGPT, Claude or any AI agent. Returns how to do it in Recruiterflow step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Recruiterflow Cloud Browser. Recruiterflow's official API: Recruiterflow has an API, but its keys are not self-serve: you ask Recruiterflow support for a key tied to your workspace (checked 23 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": "recruiterflow_create_task"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations, the description adds meaningful behavior: the tool returns step-by-step guidance (screens, buttons, fields) and does not itself open or modify anything. It also explains the API key constraint, which helps the agent understand why browser tools are needed. It does not describe the exact return format beyond 'step by step', but the read-only nature is consistent with readOnlyHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is three sentences and front-loads the purpose and behavior before adding the API key context. The API key sentence is somewhat tangential but still relevant for explaining why the browser-tool route is used. There is minor ambiguity in the opening phrase, but no redundant filler.

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 zero-parameter, guide-only tool with no output schema, the description does enough: it explains that the output is step-by-step instructions and that actual execution happens through cotlet_browser_* tools. It could be more explicit that the tool never creates the task itself, but the key operational facts are present.

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 there are no parameter semantics to clarify; the schema is empty and description coverage is 100%. The description appropriately focuses on what the tool returns rather than describing absent inputs.

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 states the tool returns step-by-step instructions for creating a task and explicitly says it opens nothing by itself. The opening phrase 'Create task in the user's own Recruiterflow account' is a bit misleading about the tool's action, but the second sentence clarifies the guide-only behavior. It does not differentiate from recruiterflow_list_tasks or other recruiterflow siblings, but it does name the cotlet_browser_* tools as the execution alternative.

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?

It clearly tells the agent what to do after using this tool: perform the task with the cotlet_browser_* tools in the Recruiterflow Cloud Browser. It implies the tool should be used to get instructions before acting, but it does not explicitly state when not to use it or contrast it with list_tasks or direct API usage.

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

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