Leadpoet

Preview adding contacts

previewCampaignAudience

Idempotent

Checks which contacts from a saved audience could join an active or paused campaign and saves a preview receipt that adding contacts requires. Nobody is added. Retrying with the same idempotencyKey and input returns the first result instead of repeating the action.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>",
      "body": "<body>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "previewCampaignAudience"
  }
}

Input Schema

Name	Required	Description
`body`	Yes
`params`	Yes
`idempotencyKey`	Yes	A unique key for this action. Reuse it only to retry the same call with the same input; use a new key for a new action.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Adds real value beyond annotations: it explains why a preview carries readOnlyHint=false ('saves a preview receipt') while reassuring 'Nobody is added', and it elaborates the idempotentHint semantics with concrete retry behavior. It does not mention authorization requirements or whether a receipt expires, which would complete the picture.

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?

Three tight sentences, front-loaded with the core action, then the safety clarification, then the retry contract. Nothing is redundant relative to the annotations or schema.

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 no output schema, the description conveys the essential outcome (which contacts could join, plus a persisted receipt) and the idempotency contract, which is enough to call it correctly. It could say more about what the preview returns and whether it must be regenerated if the audience changes.

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 33% — just idempotencyKey is documented — so the description must carry more weight. It conceptually maps the two undocumented parameters to 'saved audience' (snapshot_id) and 'campaign' (id), but never states that mapping explicitly or gives formats, leaving an agent to infer which UUID goes where.

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+resource: checks which contacts from a saved audience could join a campaign, and clarifies that nothing is added. Scope is narrowed to 'active or paused' campaigns. However, it does not distinguish itself from near-identical siblings such as previewCampaignAudienceSegment, previewAudience, or checkAudienceAvailability.

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?

Implies the usage context by stating the preview receipt is required before adding contacts, which tells an agent when this step is needed. It also narrows eligible campaigns to active or paused. It stops short of naming alternatives or stating when-not to use it, so the agent must infer routing versus the segment-preview sibling.

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

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