Skip to main content
Glama

list_email_campaign_runs

Read-onlyIdempotent

List campaign reviews and sends in the approved business, optionally filtered by campaign ID.

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_email_campaign_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
campaignIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one piece of real context — results are scoped to "the approved business" — but says nothing about ordering, page size, or that the offset param implies paging, which matters for a list tool with no output schema.

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?

One sentence, front-loaded with the action and resource, and every clause carries information. The phrasing "campaign reviews and sends" is slightly loose but not wasteful.

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

Completeness3/5

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

For a two-parameter read-only list tool with rich annotations and no output schema, this is minimally adequate: the agent knows what it fetches and that it is safe and idempotent. The paging model (offset with no stated limit) and result ordering remain undocumented, which is the main completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and it only half does: it explains that campaignId acts as an optional filter, but offset is never mentioned, and with no limit parameter the agent has no way to learn the page size or default behavior from either source.

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?

"List campaign reviews and sends" gives a specific verb plus a specific resource pair, and the campaign-ID filter narrows it further, so it reads as a distinct listing operation rather than a generic getter. It does not name sibling alternatives such as get_email_campaign_run or list_email_campaigns, so the boundary between this and those is left implicit.

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

Usage Guidelines2/5

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

The only usage signal is "optionally filtered by campaign ID," which hints at how to narrow results but never states when to pick this tool over get_email_campaign_run (single run) or list_email_campaigns (campaign definitions). No exclusions or prerequisites are given.

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.

Resources