Skip to main content
Glama

rc_create_project

Create Project in Recruiter Lite. Requires a LinkedIn Recruiter Lite seat and Linked API's Plus plan. Creation is not idempotent: after a failure, check your projects before creating again (a duplicate can only be archived). Final result: { projectId, projectUrl, name }; name may be null if it could not be read back, but the project exists.

Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.

A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "rc_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name, 1–100 characters, one line

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing async queued cloud-browser execution, the immediate {status, pendingReason, workflowId, operationName, message} response, duplicate-archive irreversibility, and the possibility that name comes back null while the project still exists. The only gap is that it doesn't state the likely latency ceiling or whether name uniqueness is enforced before queuing.

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?

Front-loaded with purpose and the non-idempotency warning, then structured into execution mechanics and pendingReason handling. It is long, but nearly every sentence prevents a concrete failure mode; the pendingReason paragraph is the only part that could be slightly tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a genuinely complex async workflow, the description carries the full burden and does so: it specifies the immediate return shape, the final result shape, the retrieval path, and how each pendingReason should be reported to the user rather than looped on.

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 100% and the single name parameter is fully documented in the schema (length, single-line constraint), so the baseline is 3. The description mentions name only in the context of the read-back result, not to add input semantics such as allowed characters or collision behavior.

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

Purpose5/5

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

Opens with a specific verb and resource ('Create Project in Recruiter Lite') and distinguishes the action from siblings like rc_archive_project, rc_rename_project, and rc_retrieve_projects. An agent knows exactly what object is produced (a project) and what the final payload looks like.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states prerequisites (Recruiter Lite seat, Linked API Plus plan), the non-idempotency rule with a concrete recovery action ('check your projects before creating again'), and the required follow-up call to get_workflow_result with the returned ids. It also gives a clear when-not: do not retry the original tool while a workflow is running.

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.