Skip to main content
Glama

LinkedIn: Select contract

linkedin_select_contract
Destructive

Select a LinkedIn Sales Navigator/Recruiter premium contract. First call linkedin_list_contracts and reuse exact contract.id. Do not pass product name or inbox_id. LinkedIn premium contract ID: Exact Sales Navigator/Recruiter contract id. Obtain with: linkedin_list_contracts -> contract.id Never pass: inbox_id, product name.

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": {
      "contract_id": "<contract_id>"
    },
    "name": "linkedin_select_contract"
  }
}

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.
contract_idYesExact premium contract ID returned by linkedin_list_contracts -> contract.id. LinkedIn premium contract ID: Exact Sales Navigator/Recruiter contract id. Obtain with: linkedin_list_contracts -> contract.id Never pass: inbox_id, product name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the mutation profile is already supplied. The description explains the prerequisite lookup and prohibited inputs, but never explains what 'selecting' actually does — whether it persists a selection, is scoped to account_id, or resets on session end — which is the key unknown for a stateful, flagged-destructive operation. No contradiction with annotations.

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?

The constraint is front-loaded, but the second half restates the same content twice: 'First call linkedin_list_contracts and reuse exact contract.id. Do not pass product name or inbox_id' is then repeated verbatim as 'Obtain with: linkedin_list_contracts -> contract.id Never pass: inbox_id, product name.' Redundant, machine-pasted phrasing wastes space without adding information.

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

Completeness3/5

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

Covers the essential lookup chain and input restrictions for a 2-parameter tool. However, for a stateful selection operation flagged destructiveHint=true with no output schema, the description should say what changes after the call and what a caller observes, which it does not.

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% and account_id is documented in the schema itself, so the baseline is 3. The description adds real meaning beyond the schema by tying contract_id's provenance to linkedin_list_contracts -> contract.id and by explicitly ruling out inbox_id and product name as substitutes, preventing a common misuse.

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: 'Select a LinkedIn Sales Navigator/Recruiter premium contract.' The scope (premium contract, not classic) is explicit, and the prerequisite tool linkedin_list_contracts is named, so an agent can distinguish this from sibling linkedin_list_contracts without opening either 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?

Gives a clear ordering rule ('First call linkedin_list_contracts and reuse exact contract.id') plus explicit anti-patterns ('Do not pass product name or inbox_id'). It is missing when-to-use guidance such as whether this is needed only when several contracts exist, or what the agent should do if no contract is found.

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.