Skip to main content
Glama

rc_sync_inbox

Sync Inbox in Recruiter Lite. Requires a LinkedIn Recruiter Lite seat and Linked API's Plus plan. Enable whole-inbox monitoring once per account, then read incoming messages with get_inbox type rc. Only messages arriving after monitoring is enabled are captured. 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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 say readOnlyHint=false and openWorldHint=true, so the description carries most of the behavioral load and does so well: it explains that the action is queued into a cloud-browser workflow taking several minutes, returns an immediate pending snapshot with status/pendingReason/workflowId/operationName/message, and returns no result data on success. It also explains the 'queued' vs 'outsideWorkingHours' pending reasons and their different polling behavior, which annotations cannot convey.

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 purpose and prerequisites are front-loaded, followed by the async workflow contract, which is well ordered for an agent. It is fairly long and the pending-workflow boilerplate is dense, but nearly every sentence (polling, no-retry rule, working-hours case) carries actionable information.

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 input parameters and no output schema, the description must explain the async return contract, which it does: the pending envelope shape, how to fetch the final result, the no-data-on-success outcome, and the two pendingReason cases. An agent has enough information to invoke it and handle every response state.

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 takes zero parameters, so the baseline is 4. The description adds relevant framing about what the call implicitly acts on (whole-inbox monitoring on the account), but there is no parameter surface to clarify.

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?

The description names a specific verb and resource ('Sync Inbox in Recruiter Lite') and immediately distinguishes it from the sibling read tool by saying to read messages with get_inbox type rc. It also states the key scope limit: only messages arriving after monitoring is enabled are captured.

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?

It gives explicit conditions: enable whole-inbox monitoring once per account, then use get_inbox to read; call get_workflow_result with the returned workflowId and operationName rather than retrying the original tool, because retrying creates duplicate queued work. Prerequisites (Recruiter Lite seat plus Linked API Plus plan) and the outsideWorkingHours case with its 'report to user rather than looping' instruction are covered.

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.