campaignstack

Enrich leads

campaignstack_enrich_leads

Run contact enrichment for up to 25 leads with bounded include flags. Email is on by default; phone must be explicitly requested and can cost more. Per-lead provider errors are returned independently. Charges vary by mode (email reveal: contact_email_reveal credits per result found; phone reveal: contact_phone_reveal credits per result found). campaignstack_estimate_cost accepts variant or variantCounts before you commit. Email is on by default; phone is charged separately only when include.phone is true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`leads`	Yes
`include`	No
`provider`	No		bettercontact
`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.
`clayRoutineId`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`items`	No
`failed`	No
`results`	No
`warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026
- removedInput schema / properties / leads / items / properties / leadSource / default
```
Removed value: -"global"
```
- addedInput schema / properties / leads / items / properties / leadSource / description
```
Added value: +"Optional. Leave it out: the server reads it from the leadId and refuses a value that disagrees."
```

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

A3.5/5.0

Behavior4/5

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

Annotations already declare openWorld/non-idempotent/non-destructive. The description adds real value beyond them: per-lead provider errors are returned independently, and billing is per result found in each mode. The per-result charge implicitly warns that re-running costs again, which is meaningful for a non-idempotent operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The final sentence repeats information already stated in the opening ('Email is on by default', phone charged only when requested), burning a whole sentence on redundancy. The cost-mode and estimate_cost guidance is front-loaded reasonably, but the duplication is wasteful.

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?

An output schema exists, so return values need not be explained, and the description covers the key behavioral facts an agent needs: scope cap, defaults, independent per-lead errors, and billing model. Minor gaps remain around provider choice and non-listed parameters.

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 only 20% and several parameters (provider, clayRoutineId, workspaceId) get no description coverage. The text does clarify include.email default true and include.phone default false with its cost implication, but it leaves the provider selection and clayRoutineId semantics unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Run contact enrichment ... leads') with a clear scope cap of 25. The resource noun distinguishes it from campaignstack_enrich_companies, but the description never names a sibling explicitly. Clear enough that an agent knows what it does.

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

Usage Guidelines3/5

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

Gives useful pre-commit guidance by pointing to campaignstack_estimate_cost with variant/variantCounts, and clarifies the email-default/phone-opt-in condition. It never states when to choose this over adjacent tools like refresh_leads, get_lead_enrichments, or enrich_companies, so usage is only implied.

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?