Skip to main content
Glama

company generate connection link

company_generate_connection_link
Idempotent

Generate or reuse a private Workspace link for connecting client channels. Set readOnly true for analytics-only personal LinkedIn profiles; Company Pages are not supported in that mode. This changes only the returned URL, not the bearer or any connected channel. Share only with the intended client. After an uncertain result retry identical arguments, never rotate.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "company_generate_connection_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
readOnlyNotrue: personal LinkedIn analytics only; false: ordinary access; omitted: ordinary link
workspaceIdYesExact ID returned by a Company tool; never a personal platformId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / readOnly
      Added value: +{
      +  "description": "true: personal LinkedIn analytics only; false: ordinary access; omitted: ordinary link",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description's added value is the scope of the effect: 'This changes only the returned URL, not the bearer or any connected channel.' That plus the retry-safety and sharing caveats gives real behavioral context beyond what the annotations encode.

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 is front-loaded in the first sentence, and each subsequent sentence carries a distinct operational fact (mode constraint, effect scope, sharing caution, retry rule). Slightly dense but nothing is wasted.

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

Completeness4/5

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

For a two-parameter, non-destructive, idempotent tool with no output schema, the description covers effect scope, mode restrictions, and failure handling. It leaves link lifetime/expiry unstated, a minor gap given the small surface.

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 baseline is 3, but the description adds a constraint not in the schema: Company Pages are unsupported in readOnly mode. That is genuine meaning beyond the enumerated 'true/false/omitted' semantics already documented.

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

Purpose4/5

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

The description opens with a specific verb pair and resource: 'Generate or reuse a private Workspace link for connecting client channels.' The 'reuse' wording plus 'never rotate' implicitly separates it from the rotate/revoke/get siblings, though no sibling is named outright.

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

Usage Guidelines4/5

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

It gives a clear conditional for the readOnly mode ('analytics-only personal LinkedIn profiles') and an explicit exclusion ('Company Pages are not supported in that mode'), plus retry guidance ('retry identical arguments, never rotate'). It does not state when to prefer company_get_connection_link over generating a new link, but usage context is otherwise solid.

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.