Skip to main content
Glama
Sign In

PersuadioAI

by com.persuadioai
OverviewDiscussionsAdmin

Get campaign status

get_campaign_status
Read-onlyIdempotent

Report recorded campaign outcomes: leads, sent records, confirmed delivery receipts, replies, opt-outs, booking records, and AI-paused leads (not people awaiting a human). Omit campaign_id to list campaigns. Account totals are independent of pagination and status filters. Read-only. Null metrics are unavailable; read the caveats before telling the operator a campaign is or is not working.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
statusNoFilter the list by status, e.g. 'active', 'draft', 'paused'.
campaign_idNoOne campaign. Omit to list all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds value by disclosing that null metrics mean unavailable, account totals are independent of pagination/status filters, and AI-paused leads are distinct from people awaiting a human. No contradiction with annotations.

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 compact and front-loaded with the outcome list, followed by list behavior, pagination semantics, and null-handling caveats. The standalone 'Read-only.' is redundant with annotations, so it is not perfectly economical.

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?

For a read-only reporting tool with no output schema, it conveys the returned metrics, list-mode behavior, pagination independence, and null interpretation. The reference to external caveats is a minor gap but the description is otherwise sufficient for an agent to call it correctly.

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 descriptions cover campaign_id and status, but limit and offset have no descriptions. The description adds meaning by explaining campaign_id omission for list mode and noting that totals ignore pagination/status filters, but it does not fully compensate for the undocumented pagination parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Report') and a concrete resource ('recorded campaign outcomes'), then enumerates the exact metrics returned. The parenthetical about AI-paused leads and the list-vs-single distinction help differentiate it from sibling tools like list_leads and get_interested_leads.

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 clear operational context: report campaign outcomes, omit campaign_id to list campaigns, and read caveats before telling the operator whether a campaign is working. It does not explicitly name when-not-to-use alternatives, so it falls short of a 5.

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

All PersuadioAI 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