Leadpoet

Preview contacts not yet messaged by segment

previewCampaignAudienceSegment

Read-onlyIdempotent

For a campaign's contacts who can leave now, lists filter options with counts (role, seniority, place, industry, company size, signal) and suggested groups, and counts how many match the given filters. Checks up to 2,000 contacts; complete says whether that was all. Saves nothing. It saves nothing, so it can be repeated.

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>"
    },
    "name": "previewCampaignAudienceSegment"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a useful 2,000-contact cap and a complete flag, but it does not explain permissions, performance beyond the cap, or what 'suggested groups' means, and the repeated 'Saves nothing' sentence adds no new information.

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

Conciseness3/5

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

The purpose and cap are front-loaded, but the first sentence is overloaded and the duplicate 'Saves nothing. It saves nothing...' wording wastes space. It remains understandable but not tightly edited.

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?

For a preview tool with nested filters and no output schema, the description covers the main behavior, contact cap, completeness flag, and non-persistence. It is still incomplete for constructing the nested filter body because most filter fields and the campaign id are not documented beyond broad categories.

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 description coverage is 0%, and the nested body.filters object has many fields with no schema descriptions. The description's categories (role, seniority, place, industry, company size, signal) only loosely map to departments, seniorities, countries/states, industries/sub_industries, company_sizes, and signals, and it does not document the required campaign id or enum values.

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?

It states a specific verb and resource: lists filter options with counts/suggested groups and counts matching campaign contacts. The title adds the 'not yet messaged' scope, but the description does not explicitly distinguish this from sibling tools such as previewCampaignAudience or previewAudience.

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?

The description implies a safe preview use case by saying it saves nothing and can be repeated. However, it gives no explicit when-to-use versus when-not-to-use guidance or named alternatives among the many preview/list siblings.

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?