Skip to main content
Glama

ADS Beast

list_outreach_campaigns

Read-only

Return a page of the email outreach campaigns, newest first, with their status, sender, offer pack, legal basis and daily limit. The reply is {campaigns, total, count, limit, offset, has_more, next_offset}; walk the pages with offset = next_offset. The letter itself is summarised as body_preview and body_chars; pass include_body = true for the full text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_outreach_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCampaigns per page. Clamped into 1..50.
offsetNoCampaigns to skip; use next_offset from the previous page.
client_idNoRestrict to one client.
include_bodyNoTrue returns each campaign's full letter (body_template); the page is then cut to fit the response size limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds ordering (newest first), the exact reply shape, and the noteworthy caveat that include_body truncates the page to fit the response size limit — useful, but that caveat is also stated in the schema, and no rate limits or permission requirements are mentioned.

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?

Three sentences, front-loaded with the return contents before the pagination mechanics and the include_body nuance. No filler, and each sentence conveys distinct operational information.

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?

There is no output schema, yet the description spells out the full reply envelope (campaigns, total, count, limit, offset, has_more, next_offset), which is exactly what an agent needs to paginate correctly. For a four-parameter read-only list tool, nothing essential is missing.

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, but the description adds real meaning: it ties offset to next_offset in the response and explains that include_body trades page size for full letter text versus the body_preview/body_chars summary. limit and client_id 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?

The description opens with a specific verb and resource ('Return a page of the email outreach campaigns, newest first') and enumerates what each record carries (status, sender, offer pack, legal basis, daily limit). 'Email outreach' implicitly separates it from list_social_campaigns, but it never names or contrasts the ambiguous sibling list_campaigns, so an agent must infer the boundary.

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?

It gives concrete operating instructions: walk pages with offset = next_offset, and pass include_body = true only when the full letter text is needed. What is missing is when to choose this over list_campaigns or outreach_campaign_check; there are no exclusions or alternative routing.

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.