Scribe Mail

Pause a marketing campaign

pause_marketing_campaign

Pause an active campaign — it stops applying to signatures. Only an active campaign can be paused (otherwise 409). Resume later with resume_marketing_campaign.

Input Schema

Name	Required	Description	Default
`id`	Yes	The campaign's UUID (the `id` from list_marketing_campaigns).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedOutput schema / properties / data / properties / name / description

Added value: +"Campaign name. Null for a legacy draft that was saved without one. Report it as an unnamed draft and refer to it by its id rather than inventing a name."

changedOutput schema / properties / data / properties / name / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed6 schema fields changedOct 28, 2026
- removedOutput schema / properties / data / properties / end_time / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / end_time / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / start_time / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / start_time / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / time_zone / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / time_zone / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare non-readOnly, non-destructive, non-idempotent, open-world, so the bar is lower; the description adds valuable context beyond them by disclosing the state precondition and the 409 failure mode. It does not discuss whether pausing affects already-issued signatures or reversibility beyond the resume pointer, leaving a small gap.

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

Conciseness5/5

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

Two compact sentences with zero filler: effect first, then precondition, then the alternative. Front-loaded and every clause earns its place.

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?

With an output schema present and full schema coverage, the description supplies the key missing behavioral facts (state requirement, error code, resume path). Only minor gaps remain, such as the exact effect on already-published signatures.

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 coverage is 100% and the id parameter is fully documented in-schema (UUID from list_marketing_campaigns); the description adds no parameter detail. Baseline 3 is appropriate since the schema carries this dimension.

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?

States a specific verb and resource ('Pause an active campaign') and describes the concrete effect ('stops applying to signatures'), which an agent cannot infer from the name alone. It is clearly distinguished from resume_marketing_campaign and delete_marketing_campaign in the sibling list.

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

Usage Guidelines5/5

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

Explicitly states the precondition (only an active campaign can be paused, otherwise 409) and names the natural follow-up tool (resume_marketing_campaign). The when-to-use condition is unambiguous.

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

All Scribe Mail tools Inspect

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.