Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Find Linkedin Url

find_linkedin_url
Read-only

For email outreach where the agent might later add LinkedIn touches, prefer setup_email_sequence(enrich=True) over calling this tool separately — enrich folds the lookup into the queue boundary so the resulting tracking row carries both identifiers.

Costs 1 Sliq credit per verified hit. Free when the user has connected their own Apollo key. Dict with success, linkedin_url, and person fields when verified; {success: False, error: ...} when Apollo returns no match; a 429 throttle adds rate_limited: True (transient — retry later, not a permanent miss).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional full name to narrow the Apollo match.
emailYesEmail address to look up.
on_behalf_ofNoAn 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest. It adds cost semantics (1 Sliq credit per verified hit, free with the user's own Apollo key), the 429 rate-limit behavior as transient vs. a permanent miss, and empty-match handling — real behavioral traits not in the annotations.

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 core purpose in the first line and uses summary/returns tags to separate concerns. It is denser than strictly necessary — the mixed-channel justification runs long — but nearly every sentence informs invocation.

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?

With no output schema, the returns block fully specifies the success shape, the failure shape, and the transient rate-limit flag. Cost, account-scoping, and error behavior are all covered, leaving nothing an agent needs to call this correctly.

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 coverage is 100% and each parameter is documented in-schema. The description mentions the email input and on_behalf_of's account context, but adds no format or syntax detail beyond the schema, so the 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+resource+input: 'Find a LinkedIn profile URL for a person given their email, using Apollo.io.' It then distinguishes itself from siblings by naming find_email as its inverse and find_phone_number as a consumer of its output, so an agent can place it precisely in the tool graph.

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?

Gives explicit scenarios (mixed-channel outreach, supplying the URL find_phone_number requires) and names a preferred alternative — setup_email_sequence(enrich=True) — with the condition that selects it. When-to-use and when-to-prefer-an-alternative are both covered.

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

All Sliq 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