Linked API

endorse_person_skills

Endorses selected skills of a 1st-degree connection, returning each selected skill's name, success and error if it failed. Skill names are in the profile owner's language. Patterns use RE2, are case-insensitive and match anywhere; anchor with ^…$ to match a whole name. Omit skillNamePatterns to endorse all skills; never pass []. An already-endorsed skill counts as success and is never removed. Each success counts toward the stEndorsements limit, including existing endorsements. The limit is checked for each skill; a failure does not stop the others, so check every item's success. If this workflow is still running, do not retry this tool; retrying can count the same skills toward the stEndorsements limit again.

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": {
      "personUrl": "<personUrl>"
    },
    "name": "endorse_person_skills"
  }
}

Input Schema

Name	Required	Description	Default
`personUrl`	Yes	Public or hashed LinkedIn URL of your 1st-degree connection.
`skillNamePatterns`	No	Optional. 1-20 RE2 patterns, each 1-200 characters, matching names in the profile owner's language. Any matching pattern selects the skill. Matching is case-insensitive and searches anywhere: manage matches Project Management; ^scrum$ matches only the whole name Scrum. Lookaround and backreferences are unsupported. Omit this parameter to endorse all skills; never pass an empty array.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds substantial context beyond that: the cloud-browser queuing model, per-skill independent success/failure, already-endorsed skills counting as success and never being removed, the stEndorsements limit applying even to existing endorsements, and duplicate-work risk on retry. The only gap is that it does not say what permissions or account tier are required to endorse.

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

Conciseness3/5

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

Purpose and the critical 'do not retry' rule are front-loaded, which is good, but the no-retry warning appears twice in near-identical form, and the RE2 matching rules are repeated verbatim from the schema. The workflow/pendingReason block is valuable but could be tightened considerably.

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 the immediate return shape ({status, pendingReason, workflowId, operationName, message}), the per-skill {name, success, error} result, and how to long-poll for completion. Nothing an agent needs to invoke this correctly and handle the async lifecycle 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?

Schema description coverage is 100% and the schema already documents RE2 syntax, case-insensitivity, anchoring, 1-20 items and the omit-vs-empty-array rule, so the description mostly restates it. The one genuinely additive note is that names are in the profile owner's language and that any matching pattern selects the skill, which clarifies multi-match 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?

States a specific verb and resource — 'Endorses selected skills of a 1st-degree connection' — plus the per-skill result shape. The singular sibling endorse_person_skill is implicitly distinguished by the plural 'selected skills' and pattern-based selection, so an agent can tell which one to pick.

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?

Explicit when-to-use rules: omit skillNamePatterns to endorse all, never pass an empty array, and route follow-up through get_workflow_result with the returned workflowId/operationName. It also states when NOT to act — do not retry while a workflow is running — and explains the outsideWorkingHours case that should be reported to the user rather than polled.

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

All Linked API 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.