Scribe Mail

List marketing campaigns

list_marketing_campaigns

Read-onlyIdempotent

List the workspace's marketing campaigns (signature banners), each with its status, schedule, targeting and content block tree. Use it to find a campaign's id before update_, schedule_, pause_, resume_, delete_ or preview_marketing_campaign; there is no single-campaign get and no server-side filter, so pick the campaign from this list. To see the rendered banner rather than its block tree, use preview_marketing_campaign. Read-only. Returns one page by default; set auto_paginate to fetch up to max_pages pages in one call, and truncated: true means more remain, so call again with a later page.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`limit`	No	Page size, 1–100 (default 50).
`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."
`max_pages`	No	Page cap when auto_paginate is true (default 5).
`auto_paginate`	No	Fetch multiple pages up to `max_pages` (default false).

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`truncated`	Yes	True when auto_paginate stopped at max_pages with more results remaining.
`pagination`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/destructive=false, so safety is covered. The description adds real behavioral context beyond them: pagination defaults, the `truncated: true` signal and what to do next, and the fact that there is no server-side filtering so the caller must pick manually. Return format is partly described but an output schema exists.

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?

Front-loaded with purpose, then usage/prerequisite constraints, then the alternative tool, then pagination mechanics. Every sentence carries distinct, actionable information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, prerequisites, sibling routing, and pagination behavior; since an output schema exists, return values need not be spelled out. An agent has everything needed to call this correctly.

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 coverage is 100%, so the baseline is 3. The description goes further by explaining the interaction between auto_paginate, max_pages, page and truncated in practical terms, which is more than the schema's terse per-field notes provide.

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 ('List the workspace's marketing campaigns (signature banners)') and immediately describes what each item contains (status, schedule, targeting, content block tree). It clearly differentiates itself from preview_marketing_campaign and the single-campaign mutation siblings.

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 names when to use it (to find a campaign's `id` before update_/schedule_/pause_/resume_/delete_/preview_), states constraints (no single-campaign get, no server-side filter), and routes the alternative use case to preview_marketing_campaign. Nothing is left to inference.

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.