Skip to main content
Glama

rc_rename_project

Rename 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. Name is required; to change only the description, pass the current name. Omit description to leave it unchanged. Final result: no result data on success.

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": "<name>"
    },
    "name": "rc_rename_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name, 1–100 characters, one line
projectIdYesProject ID as a string of digits from rc_retrieve_projects or rc_create_project
descriptionNoOmit to leave unchanged; up to 2000 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds the substantive traits: prerequisite seat and Plus-plan entitlements, asynchronous cloud-browser execution that can take minutes, an immediate {status, pendingReason, workflowId, operationName, message} return, no result data on success, and parked execution under outsideWorkingHours. These are exactly the behaviors an agent cannot infer from the annotations.

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?

Tool-specific guidance is front-loaded in the first paragraph, with async/polling mechanics after it, which is the right order. The cost is length: roughly two-thirds of the text is generic queued-workflow boilerplate that plausibly repeats across many tools, though it is load-bearing for correct invocation (no retry, poll instead).

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?

There is no output schema, and the description compensates by describing both the immediate pending snapshot and how the final result is obtained via get_workflow_result, including long-poll and in-progress-snapshot behavior. For a mutation tool with asynchronous execution and entitlement prerequisites, nothing essential is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds non-obvious semantics the schema does not: to modify only the description you must still pass the current name as a no-op, and omitting description preserves it. It also names the provenance of projectId from sibling tools, which clarifies an opaque numeric ID.

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 ("Rename Project in Recruiter Lite") and immediately anchors the target object by naming the tools that supply projectId (rc_retrieve_projects, rc_create_project). An agent can distinguish this from rc_create_project, rc_archive_project, and nv_rename_list without opening any schema.

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?

Gives explicit operating instructions: name is required, pass the current name to change only the description, omit description to leave it unchanged, and use get_workflow_result with the returned workflowId/operationName instead of retrying. It also states the don't-do case (do not retry while a workflow is running, which duplicates queued work) and how to interpret each pendingReason.

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.