Skip to main content
Glama

LinkedNav

by io.github.linglistack
OverviewDiscussionsAdmin

Create contact

create_contact

Add one LinkedIn profile as a new contact in LinkedNav (the "Contacts" page, /app/contacts). A contact and a lead are the same record (called a "prospect" once added to a campaign). Identical to create_lead. Skips silently if the profile already exists (dedup by LinkedIn URL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoThe lead's own comment on the post → {{comment}}. Leave empty for reactors (set engagerType:"reactor").
emailNoEmail address if known
intentNoFreeform note on why this contact was added / the intent signal. NOT the numeric "Intent Score" (that is auto-computed by LinkedNav).
listIdNoContact list ID to add this contact to (uses default list if omitted). Obtain list IDs via get_lists.
companyNoCurrent company name
headlineNoLinkedIn headline
icpScoreNoICP fit score 1-10 from a signal agent, if known. NOT the auto-computed Intent Score.
industryNoIndustry
jobTitleNoJob title / position
lastNameYesLast name
locationNoLocation (city, country, etc.)
firstNameYesFirst name
followUp1NoPer-lead 1st follow-up that OVERRIDES the campaign follow-up-1 template for this lead only.
followUp2NoPer-lead 2nd follow-up that OVERRIDES the campaign follow-up-2 template for this lead only.
followUp3NoPer-lead 3rd follow-up that OVERRIDES the campaign follow-up-3 template for this lead only.
icpReasonNoShort reason for the ICP score (a few words).
profileUrlYesFull LinkedIn profile URL (e.g. https://linkedin.com/in/jane-doe)
providerIdNoLinkedIn member/provider id (ACo…/ACw…) if known — e.g. the "providerId" returned by search_people. Stored as the canonical send handle so the contact stays sendable even if its URL is imperfect; only a well-formed member id is kept. A Sales Navigator id (ACw…) is kept only as a backup — invites resolve the profile URL first.
engagerTypeNoHow they engaged with the post: "commenter" (wrote a comment) or "reactor" (only liked/reacted). Powers {{action}} and lets one template fit both — {{comment}} is auto-blanked for reactors.
sourcePostUrlNoLinkedIn post URL that triggered this contact
connectMessageNoPer-lead connection-request note that OVERRIDES the campaign connect template for this lead only. Blank/omitted = use the campaign message.
sourcePostDateNoISO date the post was published → {{postDate}} (rendered as M/D).
welcomeMessageNoPer-lead welcome message (sent right after they accept) that OVERRIDES the campaign welcome template for this lead only.
sourcePostAuthorNoDisplay name of the author of the post they engaged with → {{postAuthor}} (e.g. the influencer or competitor).
sourcePostExcerptNoShort snippet of the post they engaged with → {{postText}}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-destructive mutation (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lowered. The description still adds genuinely useful, non-obvious behavior: silent skipping on duplicates and the dedup key (LinkedIn URL), plus what a contact becomes once in a campaign.

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?

Front-loads the action and target before the clarifying parenthetical. Dense but each sentence (identity, sibling equivalence, dedup) carries distinct information; the terminology digression is the only mild clutter.

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 25-param, no-output-schema tool, the description covers the important hidden semantics (dedup, record aliasing). It omits what a caller gets back on success versus skip, which matters slightly more because there is no output schema.

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 25 parameters are richly documented in the schema itself, so baseline 3 applies. The description's only param-relevant signal is the profileUrl dedup key, which is behavioral rather than adding field-level meaning.

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+resource ("Add one LinkedIn profile as a new contact") and grounds it in the product UI ("Contacts" page, /app/contacts). It explicitly names the sibling create_lead and declares equivalence, so the agent can distinguish it from other create_* tools without opening a schema.

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?

Identifies the direct alternative (create_lead) and asserts they are identical, which helps selection. It also explains record identity (contact/lead/prospect) and silent-skip dedup, but gives no explicit when-to-use vs bulk siblings like create_leads_bulk or add_lead_to_campaign.

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

All LinkedNav toolsInspect
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.

Resources