Skip to main content
Glama

Preview Reactivation Campaign Tool

preview-reactivation-campaign
Read-only

Previews dormant customers eligible for one authorized reactivation campaign without sending or changing records. Use to preview reactivation 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-reactivation-campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum audience items to evaluate.
campaign_idYesReactivation campaign ID returned by search-reactivation-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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'without sending or changing records' is largely reinforcement rather than new information. The mention of returned keys sends/mutates adds mild confirmation that no side effects occur, but permissions, cost of evaluating the audience, or truncation behavior for the limit cap are not discussed.

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 purpose and safety constraints are front-loaded in two tight sentences with no filler. The trailing enumeration of return keys is somewhat wasteful given an output schema exists, but it does not bury the core statement.

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 low-complexity, read-only preview with full schema coverage, annotations, and an output schema, the description covers what an agent needs to call it correctly. The return-field list is redundant against the output schema, and the absence of guidance on obtaining campaign_id is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are self-documenting, so the baseline of 3 is exceeded only slightly: the description adds that the preview targets 'dormant customers eligible' for a single authorized campaign, which frames what campaign_id selects. The limit parameter and its 50-item cap are left entirely to 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?

Names a specific verb and resource ('Previews dormant customers eligible for one authorized reactivation campaign') and scopes it to a single campaign, which distinguishes it from preview-broadcast-campaign and preview-referral-campaign. It does not explicitly name those siblings, so differentiation is inferred from the domain noun rather than stated.

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?

The sentence 'Use to preview reactivation campaign in the connected business' largely restates the purpose rather than describing when to select this over alternatives. The only real guidance is the negative framing 'without sending or changing records', with no explicit when-not conditions or prerequisite ordering (e.g., first obtaining campaign_id via search-reactivation-campaigns).

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