Leadpoet

Save overrides to an ICP

promoteIcpOverrides

DestructiveIdempotent

Saves field changes made for one use, such as a lead request or campaign, back to the ICP as its new published version, or to the selected Product connection. 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": "promoteIcpOverrides"
  }
}

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

B3.4/5.0

Behavior4/5

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

The annotations already mark the operation as destructive and idempotent, and the description adds useful behavioral context: it creates a new published ICP version or updates the selected Product connection, and retrying with the same idempotencyKey and input returns the first result. It does not detail permissions or what existing state is superseded, but it meaningfully supplements the annotations.

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?

The description is two tight sentences: the first states the operation and target, the second covers retry behavior. It is front-loaded and contains no unnecessary wording.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, nested mutation with low schema description coverage and no output schema. The description covers the high-level action and idempotency, but omits important context such as concurrency expectations, product-selection behavior, override limits, and failure semantics for expected_current_version_id.

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 only 33%, and the description explains essentially no parameters beyond referencing idempotencyKey retry behavior. It does not clarify expected_current_version_id, product_selection, surface values, or override path semantics, leaving most of the nested body undocumented.

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 clearly states that the tool saves field overrides back to the ICP as a new published version, or to a selected Product connection. It is specific enough to distinguish this from draft editing, though it does not explicitly name sibling tools like publishIcp or updateIcpDraft.

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?

It implies the tool is used when changes made for a specific use, such as a lead request or campaign, should be promoted back to the ICP. However, it does not state when to choose this over publishIcp, updateIcpDraft, or other ICP-related sibling tools, nor does it describe prerequisites or exclusions.

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?