Leadpoet

Get campaign decisions

getCampaignDecisions

Read-onlyIdempotent

Returns campaign planning decisions with actions, reason codes and human overrides. Paged lookups include a continuation cursor; MCP and the Agent default to the latest 10. The legacy snapshot contains the latest 200 decisions.

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

Input Schema

Name	Required	Description	Default
`query`	No
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on behavior annotations cannot express: pagination semantics, a continuation cursor, and caller-specific default page sizes. The unexplained 'legacy snapshot' of 200 decisions is the one behavior left ambiguous — it is not clear what selects it.

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?

Three dense sentences, front-loaded with the return payload, then paging, then snapshot scope — no filler. Slight density cost in the elliptical 'legacy snapshot' clause, which is stated without context.

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?

No output schema exists, and the description does list the returned fields, which is good. However, for a nested two-parameter tool the required identifier's meaning and the mechanism that produces the 'legacy snapshot' path remain unexplained, leaving real gaps 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 description coverage is reported as 0%, so the description must compensate; it explains `limit`/paging and the continuation cursor, but the required `id` parameter is never mentioned — the agent must infer from the tool name that it is a campaign identifier. Nested `query` vs top-level `params` structure is also unaddressed.

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 ('Returns campaign planning decisions') and enumerates the payload contents (actions, reason codes, human overrides). It is clear what the tool retrieves, but it never contrasts itself with the many sibling getCampaign* tools, so sibling differentiation is left to inference.

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?

No explicit when-to-use or when-not-to-use guidance against alternatives. It does implicitly convey usage context by describing caller-dependent defaults ('MCP and the Agent default to the latest 10', legacy snapshot 'latest 200'), which helps an agent predict what it will get, but the routing decision between this and siblings is unaddressed.

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?