Skip to main content
Glama

rc_archive_project

Archive Project in Recruiter Lite. Requires a LinkedIn Recruiter Lite seat and Linked API's Plus plan. Use projectId from rc_retrieve_projects or rc_create_project. Safe to repeat. Final result: { alreadyArchived }, true when the project was already archived and nothing changed.

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": {
      "projectId": "<projectId>"
    },
    "name": "rc_archive_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject ID as a string of digits from rc_retrieve_projects or rc_create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=false and openWorldHint=true, so the description carries the real burden and does it well: idempotency ('safe to repeat'), the queued cloud-browser execution model, an immediate {status: 'pending'|'running', pendingReason, workflowId, operationName, message} envelope, and the final {alreadyArchived} result. It further distinguishes pendingReason values ('queued' vs 'outsideWorkingHours') and explains that the latter returns immediately rather than polling, which is exactly the kind of behavior an agent would otherwise mishandle.

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?

Purpose, prerequisites, follow-up tool, and pending-reason semantics are front-loaded in that order, and no sentence is filler. It runs long due to the shared async-workflow boilerplate, but the length is justified by genuinely distinct failure modes being covered.

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, the description still describes both possible return shapes (the pending snapshot and the {alreadyArchived} final result) and how to convert the former into the latter. For a one-parameter asynchronous mutation, nothing an agent needs in order to call it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines the digit-string project ID and its provenance. The description repeats the same sourcing hint from rc_retrieve_projects or rc_create_project without adding format, validation, or edge-case semantics beyond it.

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?

States a specific verb and resource ('Archive Project in Recruiter Lite') and scopes it to the Recruiter Lite/Plus plan context. An agent can immediately distinguish this mutation from siblings like rc_create_project or rc_retrieve_projects.

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 names where projectId comes from (rc_retrieve_projects or rc_create_project), states it is safe to repeat, and gives a clear directive on the follow-up tool (get_workflow_result with the returned workflowId and operationName). It also gives an explicit when-not-to-use rule: do not retry the original tool while a workflow is running because that creates duplicate queued work.

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.