Skip to main content
Glama
Sign In

Leadpoet

by com.leadpoet
OverviewDiscussionsAdmin

Get a campaign

getCampaign
Read-onlyIdempotent

Returns one campaign's settings, status, AI planning budget and contact counts by enrollment status. When enrollment_counts_limited is true the counts cover only part of the campaign: say at least. stopped includes contacts removed from the campaign. waiting is every contact still in the sequence between steps, already messaged or not yet: never call it not yet contacted. summary.contacted_count is how many were contacted; not yet messaged is summary.enrollment_count minus contacted_count. Archived campaigns are not returned.

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": "getCampaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: archived campaigns are excluded, counts may be partial when enrollment_counts_limited is true, and specific field semantics (stopped, waiting, contacted_count) are defined. It does not describe error behavior for a missing or archived id.

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?

Front-loaded with the return summary, then dense field-semantics sentences with no filler. Slightly long, but each sentence carries distinct information about interpreting counts.

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?

No output schema exists, so the description must explain return values, and it does so thoroughly for the count fields. It is nearly complete for a single-id read tool; only the id parameter and error/not-found behavior are unaddressed.

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?

Only one parameter (id, uuid) and schema description coverage is 0%, so the description would ideally clarify it, but it never mentions the id at all. The parameter is self-evident from its name and format, so the gap is minor, but the description adds no meaning beyond 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?

States a specific verb and resource ('Returns one campaign') and enumerates the returned content: settings, status, AI planning budget, and contact counts by enrollment status. This distinguishes it from the narrower siblings like getCampaignMessaging or getCampaignActivity, though it never explicitly routes the agent to those alternatives.

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?

Provides interpretation guidance (how to read enrollment_counts_limited, stopped, waiting, contacted_count) and a scope constraint (archived campaigns are not returned), but gives no explicit when-to-use-this-vs-sibling guidance. Usage is implied by the field list rather than stated.

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

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