Leadpoet

Create a lead request

createRequest

DestructiveIdempotent

Useful when the user wants new B2B leads: companies that match an ideal customer profile (ICP), with the right contacts at each. Starts a lead request: Leadpoet researches companies and contacts that match the targeting and delivers them to Pipeline, with a typical turnaround of 1–2 days. Reserves credits. With recurrence, also schedules paid repeats that add contacts to a campaign. 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": {
      "body": "<body>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "createRequest"
  }
}

Input Schema

Name	Required	Description	Default
`body`	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?

Beyond the annotations, the description adds useful behavior: typical turnaround, credit reservation, recurrence scheduling, and idempotent retry semantics. It does not clarify whether reserved credits are refundable or cancelable, or what happens on partial failure, which are relevant given destructiveHint=true.

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?

The description is front-loaded and mostly efficient, with each sentence contributing useful context. The standalone 'Reserves credits.' is effective, but the recurrence sentence refers to a capability that is not visible in the schema, slightly reducing precision.

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 complex tool with a deeply nested body and no output schema, the description covers the high-level workflow but omits what a successful call returns and common failure modes. It also mentions recurrence even though the input schema exposes no recurrence parameter, leaving an important gap for correct invocation.

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 50%, and the large nested body contains many fields such as icp_id, supplied_companies, signal_profile, and credit_budget that the description does not explain. The description adds meaningful idempotencyKey retry semantics, but most parameter meaning must still come from the schema.

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?

The description uses a specific verb and resource: it starts a lead request for B2B companies matching an ICP with the right contacts. It is clear what the tool does, but it does not explicitly distinguish this from the sibling requestContacts tool.

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?

It gives a clear usage context: use when the user wants new B2B leads matching an ICP. It does not provide exclusions, prerequisites, or named alternatives, so it falls short of full when/when-not guidance.

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?