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.

Input Schema

TableJSON 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	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.
`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 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.5/5.0

Behavior4/5

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

readOnlyHint=true already covers the safety profile, but the description adds real value beyond annotations: it warns that 'position' and 'company' are connection-time snapshots that may be stale, and it documents the return shape (count, truncated flag, connections array). It stops short of stating auth/credit implications, which the on_behalf_of parameter hints at.

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 purpose and resource, then the exclusions, then the staleness caveat, with return values isolated in a dedicated tag. Every sentence carries information; no 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?

There is no output schema, yet the description supplies a <returns> block covering count, truncated, and the connections array, plus the staleness caveat and sibling routing. For a read-only search tool this is fully sufficient for correct invocation.

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 the schema already documents all five parameters including the allowed where_clause columns. The description only adds a pointer ('Use the exact column names listed under where_clause below'), which is useful signposting but not new semantic content. Baseline 3 applies.

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') and names the underlying table. It also names the siblings it is NOT ('search_linkedin_message_history', 'query_prospects'), so an agent can select 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?

Explicitly frames when to use it ('find existing relationships by name, title, or company') with concrete example queries, and names the two alternatives plus the condition that selects them. Nothing is left to inference.

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?