campaignstack

Get leads

campaignstack_get_leads

Read-onlyIdempotent

Read leads by ids or search filters in one bounded V2 envelope. Includes are capped; campaign-specific scoreBreakdown requires campaignId. Use this instead of legacy search/get pairs when the user needs leads plus selected context. It does not modify leads or enqueue outreach. 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

TableJSON Schema

Name	Required	Description
`ids`	No	Specific lead IDs to hydrate. Max 25.
`limit`	No
`query`	No	Name, email, or LinkedIn URL search when ids are omitted.
`cursor`	No
`include`	No
`companyId`	No	Restrict search to leads attached to this company.
`campaignId`	No	Required when include.scoreBreakdown is true.
`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.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

changedInput schema / properties / include / properties / mutualConnections / description

Previous value: -"Previously recorded LinkedIn connection edges only, not a live crawl of the lead's full network. Absence of an edge means not yet observed, not that none exists."New value: +"Previously recorded LinkedIn connection edges only, not a live crawl of the lead's full network. Absence of an edge means not yet observed, not that none exists. Returns { connections, total }, total being the count returned under the limit."

addedInput schema / properties / include / properties / mutualConnectionsDegree

Added value: +{
+  "description": "Only with mutualConnections: keep edges of this observed degree.",
+  "enum": [
+    "1st",
+    "2nd",
+    "3rd",
+    "out_of_network"
+  ],
+  "type": "string"
+}

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.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description adds real behavioral context: includes are capped, scoreBreakdown is campaign-scoped, results are a single page, and pagination must be followed before counting. No contradiction with 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 purpose in the first clause, then layers constraints and pagination guidance. Six sentences are mostly justified, though the pagination instruction is slightly verbose for a description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values needn't be described, and annotations carry the safety profile. The description fills in the operationally important gaps: include caps, the campaignId dependency, and one-page pagination behavior. Complete enough to call 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 63% and the schema already documents the campaignId/scoreBreakdown dependency and the ids/query roles, so the description adds little parameter meaning beyond restating the include cap and campaignId requirement. Baseline 3 for partially-covered params is appropriate.

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 (Read) and resource (leads) plus the two access modes (by ids or search filters), and explicitly positions itself against 'legacy search/get pairs.' An agent can tell it apart from write siblings like edit_leads or enrich_leads without opening the schema.

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?

Gives a clear selection rule: use this instead of legacy search/get pairs when the user needs leads plus selected context, and clarifies it does not modify leads or enqueue outreach. It stops short of naming the specific sibling read tools (e.g. get_lead_enrichments) it might compete with, so no explicit exclusions.

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?