Skip to main content
Glama

Preview Broadcast Campaign Tool

preview-broadcast-campaign
Read-only

Previews one approved broadcast audience, including suppression and policy skips, without sending or changing records. Use to preview broadcast campaign in the connected business. Returns campaign, assistant_run, requested, eligible, skipped, items, sends, mutates, scope.

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": "preview-broadcast-campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum audience items to evaluate.
campaign_idYesBroadcast campaign ID returned by search-broadcast-campaigns.

Output Schema

NameRequiredDescriptionDefault
itemsYesBounded items records returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
sendsYesSends flag; previews do not perform this action.
mutatesYesMutates flag; previews do not perform this action.
skippedYesSkipped for the returned result.
campaignYesCampaign data returned by the authorized safe projection.
eligibleYesEligible for the returned result.
requestedYesRequested for the returned result.
assistant_runYesAssistant run metadata; empty collections retain their existing JSON array representation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "campaign_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "assistant_run": {
      +      "description": "Assistant run metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "campaign": {
      +      "description": "Campaign data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "eligible": {
      +      "description": "Eligible for the returned result.",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "description": "Bounded items records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "mutates": {
      +      "description": "Mutates flag; previews do not perform this action.",
      +      "enum": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "requested": {
      +      "description": "Requested for the returned result.",
      +      "type": "integer"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "sends": {
      +      "description": "Sends flag; previews do not perform this action.",
      +      "enum": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "skipped": {
      +      "description": "Skipped for the returned result.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "campaign",
      +    "assistant_run",
      +    "requested",
      +    "eligible",
      +    "skipped",
      +    "items",
      +    "sends",
      +    "mutates",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add real context beyond that: the preview includes suppression and policy skips, which explains what the agent will see. However, the trailing field list ('campaign, assistant_run, requested, eligible, skipped, items, sends, mutates, scope') is redundant with the output schema and adds no behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well-formed and front-loaded, but the second is a tautological restatement of the tool name and the third is a raw field dump that duplicates the output schema. Roughly a third of the text does not earn its place.

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?

With annotations covering safety and an output schema covering return shape, the definition covers the essentials for a read-only preview. It leaves gaps on the more interesting parts: what 'suppression and policy skips' actually mean, whether the limit caps pagination, and the precondition that the campaign be approved.

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 100%, so both parameters (campaign_id, limit) are already fully documented with bounds and defaults. The description only implies that the target is 'one approved broadcast audience', which mildly reinforces the approved-campaign requirement but adds nothing about the limit semantics.

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 names a specific verb and resource ('Previews one approved broadcast audience') and scopes it with 'without sending or changing records', which separates it from write-path siblings. The 'broadcast' qualifier distinguishes it in spirit from preview-reactivation-campaign and preview-referral-campaign, though the description never explicitly contrasts them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use to preview broadcast campaign in the connected business' restates the tool name rather than giving a real usage condition. It does not say when to prefer this over the other preview-* siblings, nor does it state the prerequisite that the campaign must already be approved (that hint only appears in the schema text for campaign_id).

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.

Resources