Scribe Mail

Resume a marketing campaign

resume_marketing_campaign

Resume a paused campaign — it becomes active again. Only a paused campaign with a future end time can be resumed (otherwise 409). Returns 403 if the workspace's plan does not include marketing campaigns.

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": {
      "id": "<id>",
      "context": "<context>"
    },
    "name": "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

Behavior5/5

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

Goes well beyond annotations by disclosing both preconditions and the two failure modes: 409 for ineligible state, 403 when the workspace plan lacks marketing campaigns. That plan-gating detail is exactly the kind of context annotations cannot express.

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 short sentences, front-loaded with the state transition, followed immediately by constraints and error codes. No filler or repetition of the title.

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 annotations covering the safe-but-mutating profile, the description supplies everything needed to attempt the call correctly. A minor gap is that it doesn't say what the returned campaign object reflects (new status, schedule), though the output schema likely covers that.

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%, and the schema already explains that 'id' is the UUID from list_marketing_campaigns and fully specifies the 'context' analytics field. The description adds no parameter-level detail, so the baseline 3 applies.

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?

Specific verb ('Resume') plus resource ('a paused campaign') plus the resulting state ('it becomes active again'). This cleanly separates it from pause_marketing_campaign and update_marketing_campaign without the agent needing to open a schema.

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?

Gives an explicit eligibility gate — the campaign must be paused and have a future end time — and names the failure code (409) when that gate is not met. It does not cross-reference the sibling pause/update tools, so it stops short of a full when/when-not/alternatives statement.

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.