campaignstack

Export LinkedIn connections

campaignstack_export_linkedin_connections

Start a runner job that exports an account's first-degree LinkedIn connections into a lead list. This does not send connection requests.

Input Schema

Name	Required	Description
`listName`	No
`accountId`	No	The account to use (LinkedIn account ID). Omit it to default to the workspace's only LinkedIn account that is ready; with several, the error lists them (id and name) so you can ask the person which one.
`workspaceId`	No	Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.
`keepUpToDate`	No
`maxConnections`	No

Output Schema

Name	Required	Description	Default
`ok`	No
`item`	No
`results`	No
`warning`	No
`nextStep`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / accountId / description

Added value: +"The account to use (LinkedIn account ID). Omit it to default to the workspace's only LinkedIn account that is ready; with several, the error lists them (id and name) so you can ask the person which one."

removedInput schema / required
```
Removed value: -[
-  "accountId"
-]
```

Changed2 schema fields changedSep 29, 2026

addedInput schema / properties / workspaceId / description

Added value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."

changedInput schema / required

Previous value: -[
-  "workspaceId",
-  "accountId"
-]New value: +[
+  "accountId"
+]

AddedSep 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations declare a non-read-only, open-world, non-idempotent operation, and the description usefully adds that the work runs as an asynchronous runner job and that no connection requests are sent. It still omits operational traits such as how long the job takes, how to track its status, or that repeating it creates a new run.

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?

Two short sentences with the action front-loaded and zero filler; the negative scoping clause earns its place by preventing a common confusion.

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?

An output schema exists, so return values need no explanation, and the async nature is disclosed. However, the three undescribed parameters and total absence of usage context leave the definition only minimally adequate for a job-launching mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%: listName, keepUpToDate, and maxConnections have no schema descriptions, and the description never mentions any of the five parameters. With three undocumented inputs, the description fails to compensate for the coverage gap.

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 (start a runner job that exports), a specific resource (an account's first-degree LinkedIn connections), and the destination artifact (a lead list). The closing negative clause explicitly separates it from campaignstack_send_connection_request and other outreach siblings.

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

Usage Guidelines2/5

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

No when-to-use conditions, prerequisites, or alternatives are given. The agent must infer from the name that this is the export path versus campaignstack_import_leads or campaignstack_export_leads_to_crm; nothing in the text routes it.

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

All campaignstack 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?