Sliq

Search LinkedIn connections

search_linkedin_connections

Read-only

position and company are connection-time snapshots and may be stale — treat them as a starting point, not current ground truth. Dict with count, truncated (True when more rows exist past this page), and connections array.

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": {
      "where_clause": "<where_clause>"
    },
    "name": "search_linkedin_connections"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default 50, max 200). Only override if the user says a specific number. For vague quantities ("a few", "recent"), omit this parameter to use the default.
`offset`	No	Rows to skip for paging (default 0). When the result is truncated, re-call with offset += limit to fetch the next page.
`order_by`	No	SQL ORDER BY clause (default: added_date DESC).	added_date DESC
`on_behalf_of`	No	A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
`where_clause`	Yes	SQL WHERE clause (without WHERE keyword). Use ONLY these columns: first_name, last_name, position, company, url, email_address, connected_on, linkedin_provider_id, added_date.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / on_behalf_of / description

Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / on_behalf_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}

First observedSep 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries real weight and it delivers: it warns that position and company are connection-time snapshots that may be stale and should be treated as a starting point. It also documents the return shape (count, truncated, connections array) in the absence of an output schema. It does not restate paging behavior, which the schema already covers.

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?

Front-loaded with the core identity, then examples, then exclusions, then a caveat, all inside clearly delimited summary/returns blocks. Every clause carries operative information; nothing is padding.

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 filtered-search tool with five parameters and no output schema, the definition covers purpose, alternatives, column constraints, data-freshness caveats, and the return shape. An agent has everything needed to call it correctly and interpret the result.

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 the baseline is 3, but the description adds a targeted operational constraint by pointing at the exact column names allowed in where_clause, which preempts the common failure of inventing column names. It does not add syntax examples for where_clause, leaving that to the schema.

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 ('search the user's established first-degree LinkedIn connections'), even naming the underlying table, and gives two concrete example queries. It explicitly excludes sibling territory (message history, prospects), so an agent can distinguish it without opening another schema.

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

Usage Guidelines5/5

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

Names the conditions that select this tool (finding existing relationships by name, title, or company) and explicitly routes away with named alternatives: search_linkedin_message_history for messages and query_prospects for outreach prospects. Both when-to-use and when-not-to-use are covered.

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

All Sliq tools Inspect

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

Need Help?