Skip to main content
Glama

Create a LinkedIn sign-in link

create_linkedin_connect_link
Destructive

Use this when the user wants to connect a LinkedIn seat. Makes a hosted sign-in link, valid for 24 hours, for the seat's owner to open and sign in to LinkedIn on, so nobody else handles their password. Keep the link private: whoever opens it can connect a seat to the organization. Making the link is free; once a seat connects, it costs $10 for each 30 days it stays connected, charged to the organization's balance. Refused when the balance cannot cover the first 30 days, or when every seat the organization may have is in use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses link validity duration, privacy/security expectations, the free creation versus $10 per 30 days connection cost, balance-based refusal, and seat-exhaustion refusal. These are exactly the behavioral traits an agent needs to set expectations and explain outcomes. Nothing here contradicts 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.

Conciseness5/5

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

The description is front-loaded with the use case, then adds mechanism, privacy constraint, pricing, and refusal conditions in a compact sequence. Every sentence contributes actionable information, and none of it is filler.

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?

For a zero-parameter tool with no output schema, the description covers the important context: what is created, how long it lasts, who should open it, what it costs, and when it will be refused. An agent can call and explain this tool without further information.

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 there is no parameter semantics to explain; the baseline for this dimension is 4. The description correctly adds no irrelevant parameter detail.

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 states a specific action and resource: making a hosted LinkedIn sign-in link for a seat. It is immediately clear what the tool produces. It does not explicitly distinguish this from the sibling reconnect-link tool, which keeps it from a 5.

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?

The opening sentence gives clear when-to-use guidance: when the user wants to connect a LinkedIn seat. It also states refusal conditions, which help an agent anticipate failures. It stops short of naming alternatives or explicitly saying when not to use this versus the reconnect-link sibling.

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.

Resources