campaignstack

Get lead lists

campaignstack_get_lead_lists

Read-onlyIdempotent

Read lead lists by ids, or list a campaign's or the workspace's lead lists, narrowed by origin (source) or by LinkedIn account (accountId: that account's connections, invited and post engagers lists). Optionally includes a bounded page of members. Use this when the user asks which lists exist or who is in them; it does not add or remove members. Results are one page. When pagination reports more, say so rather than presenting the page as the whole set, and page through before counting anything.

Input Schema

Name	Required	Description
`ids`	No	Specific lead-list IDs. Max 25.
`limit`	No
`cursor`	No
`source`	No	Only lists of this origin. linkedin_connections, linkedin_invited (people the account's workflows sent a connection request to) and linkedin_post_engagers (people who reacted to, commented on or reposted the account's posts) are the lists a LinkedIn account owns; the last two are kept up to date by CampaignStack and their members cannot be edited.
`accountId`	No	Only the lists this LinkedIn account owns in the workspace (its connections, invited and post engagers lists).
`campaignId`	No	List lead lists in this campaign when ids are omitted. Without it, the workspace's lists are listed.
`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.
`includeMembers`	No

Output Schema

Name	Required	Description	Default
`items`	Yes
`warnings`	No
`missingIds`	No
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 12, 2026

addedInput schema / properties / accountId

Added value: +{
+  "description": "Only the lists this LinkedIn account owns in the workspace (its connections, invited and post engagers lists).",
+  "type": "string"
+}

changedInput schema / properties / campaignId / description

Previous value: -"List lead lists in this campaign when ids are omitted."New value: +"List lead lists in this campaign when ids are omitted. Without it, the workspace's lists are listed."

addedInput schema / properties / source

Added value: +{
+  "description": "Only lists of this origin. linkedin_connections, linkedin_invited (people the account's workflows sent a connection request to) and linkedin_post_engagers (people who reacted to, commented on or reposted the account's posts) are the lists a LinkedIn account owns; the last two are kept up to date by CampaignStack and their members cannot be edited.",
+  "enum": [
+    "manual",
+    "import",
+    "event",
+    "group",
+    "scheduled_sync",
+    "linkedin_connections",
+    "linkedin_invited",
+    "linkedin_post_engagers"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New 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."

AddedSep 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that results are a single bounded page, that pagination may report more, and that the agent must page through before counting or presenting results as complete. That is exactly the operational context annotations cannot carry.

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?

Five dense sentences, front-loaded with the access modes, then filters, then the usage trigger, then the pagination caveat. No filler; each sentence carries operational information.

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 an output schema present, return shape need not be explained. The description covers access modes, filter semantics, mutation exclusion, and pagination behavior — everything an agent needs to call and interpret 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?

At 63% schema coverage, the schema already documents ids, source, accountId, campaignId and workspaceId richly. The description adds the ids-vs-campaignId-vs-workspaceId precedence and the accountId/source relationship, but says nothing about limit or cursor and only hints at includeMembers. Baseline 3 for mostly-covered params with partial added value.

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 (read/list lead lists) and enumerates the three access modes — by ids, by campaign, or by workspace — plus the narrowing filters (source, accountId). An agent can distinguish this from campaignstack_delete_lead_list and campaignstack_edit_lead_list immediately.

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?

"Use this when the user asks which lists exist or who is in them; it does not add or remove members" gives a clear when-to-use and an explicit when-not (membership mutation). It also instructs the agent to page through before counting. It stops short of naming the sibling that handles member changes or reads leads within a list.

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?