Skip to main content
Glama

ADS Beast

outreach_campaign_check

Read-only

Run the pre-launch check of one email outreach campaign: who may be emailed under its legal basis, why the others are blocked (consent, personal mailbox, country, unsubscribed), and sender problems. Blocker issues stop the campaign from being activated.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "outreach_campaign_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesEmail campaign id.

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 establish the read-only, non-destructive, open-world profile, and the description usefully adds behavioral context beyond them: it summarizes the categories of findings returned and, critically, that blocker-severity findings prevent campaign activation. It does not describe output structure or whether results are cached/point-in-time, which keeps it short of a 5.

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?

Two sentences, front-loaded with the action and followed by the consequence of blockers. The parenthetical list of block reasons is dense but each item earns its place by telling the agent what the output will contain. Minor awkwardness from packing everything into one long first sentence.

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, single-parameter check with no output schema, the definition supplies enough: what is evaluated, what classes of findings come back, and what a blocker means for the campaign. Missing only whether the check is expensive/slow or whether it must be re-run after edits.

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?

There is a single required parameter with full schema description coverage ('Email campaign id.'), so the schema already carries the meaning. The description adds no constraints or format hints about campaign_id, which is the expected baseline when the schema is complete.

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 definition states a specific verb and resource ('Run the pre-launch check of one email outreach campaign') and enumerates what the check reports: eligible recipients under the legal basis, why others are blocked (consent, personal mailbox, country, unsubscribed), and sender problems. That is far more concrete than a tautology, but it never distinguishes itself from similarly named siblings such as campaign_draft_publish_check or the various *_check tools.

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?

Usage context is implied: this is the step taken before activating a campaign, and the definition notes that blocker issues stop activation. It provides no explicit when-not guidance, no prerequisites (does the campaign need a draft first?), and does not name an alternative tool for other stages of review.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.