Skip to main content
Glama

LinkedIn: Visit profile

linkedin_visit_profile
Destructive

Report a LinkedIn profile visit using notify_visit_token returned by the resolved profile. The token is provider-issued and must not be replaced with user_id, profile URL or public identifier.

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": {
      "notify_visit_token": "<notify_visit_token>"
    },
    "name": "linkedin_visit_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
notify_visit_tokenYesExact notify_visit_token returned by linkedin_get_profile_from_url/linkedin_get_profile for the profile being visited; never invent it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is largely covered. The description adds a genuinely useful constraint about token provenance but does not disclose the actual side effect — that the visit becomes visible to the profile owner — nor what a 'destructive' visit entails. No contradiction with the annotations, but the behavioral picture stays thin.

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?

Two tight sentences, front-loaded with the action and followed by the token constraint; nothing is padding. It is efficient, though the brevity leaves the agent with no cues about side effects or return behavior.

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?

Only two parameters, full schema coverage, and annotations that declare the safety posture, so the description covers the essentials. What is missing is the post-call picture: there is no output schema yet the description says nothing about what a successful report returns or whether the visit is observable to the target, which matters for a destructive-flagged action.

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%, so both parameters are already documented in the schema, including the warning not to invent the token. The description restates that constraint (provider-issued, do not substitute user_id/profile URL/public identifier) with added emphasis but no new syntax, format, or failure-mode information. Baseline 3 applies when the schema carries the load.

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 and resource ("Report a LinkedIn profile visit") and pins it to a token produced by a prior resolution step. That is enough for an agent to tell this apart from read-only siblings like linkedin_get_profile or linkedin_get_profile_from_url, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent must first resolve a profile and then call this with the returned token. There is no explicit when-to-use/when-not-to-use framing, no statement of what happens if the visit is reported repeatedly (idempotentHint=false), and no mention of credit or rate costs.

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.