Skip to main content
Glama
Sign In

Webanto

by com.webanto
OverviewDiscussionsAdmin

List organization email campaigns

webanto_list_email_campaigns
Read-onlyIdempotent

Read a bounded live page of this organization's campaigns and exact versions. Existing native campaign drafts, provider delivery and human engagement are separate facts. No send, credits or provider calls. Use an exact version when preparing a send; newly granted email:read is required.

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": "webanto_list_email_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
after_idNoOpaque next_cursor from the preceding page with the same filters.
page_sizeNoMaximum campaigns in this live page; at most 20.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the description adds limited extra value. It does supply genuinely new context: no send, credit, or provider calls are triggered, the page is 'live' rather than cached, and a newly granted email:read scope is required. However, negatives such as 'drafts, delivery and engagement are separate facts' are too vague to tell the agent what the payload actually excludes.

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?

It is short and the read/scope constraint is stated first, which is good. The middle sentence about 'separate facts' is dense and hard to parse, so it wastes some space without clearly telling the agent anything actionable.

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, full parameter coverage, and read-only annotations, the remaining needs are permission and side-effect disclosure, both of which are present. Missing is any pointer to the singular get tool or the report tool when the agent needs detail beyond the bounded page.

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%, so after_id and page_size are already fully documented. The description adds only the general idea of a bounded page and mentions no cursor, page-size cap, or filter syntax, so it does not go beyond 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 first sentence names a specific verb and resource ('Read a bounded live page of this organization's campaigns and exact versions'), which distinguishes it from the singular sibling webanto_get_email_campaign. However, the terms 'exact versions' and 'separate facts' are internal vocabulary that an agent cannot resolve without opening other tools.

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?

'Use an exact version when preparing a send' gives one narrow usage context, but there is no explicit routing between this list tool, webanto_get_email_campaign, webanto_get_email_report, and webanto_get_email_send_run. The agent must infer which one to reach for when it wants delivery or engagement data.

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

All Webanto toolsInspect
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.

Resources