Skip to main content
Glama

Supovia Customer Support

by com.supovia
OverviewDiscussionsAdmin

List email campaigns

list_campaigns
Read-onlyIdempotent

Use this when someone asks which email campaigns one of their websites has. Returns each campaign's id, name and created and edited times, 20 per page by default (no recipients, subject or content). Not for sending a campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoCampaigns per page, from 1 to 50; defaults to 20
cursorNoThe page.nextCursor of the previous page for the same website; absent for the first page
websiteIdYesWebsite whose campaigns to list

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYeshasMore is true when more campaigns follow; pass nextCursor as cursor to get them
campaignsYesCampaign identity only. Recipient lists, subjects, message content, user ids, organization ids and arbitrary metadata are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous call"New value: +"The page.nextCursor of the previous page for the same website; absent for the first page"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum campaigns per page (default 20)"New value: +"Campaigns per page, from 1 to 50; defaults to 20"
    • changedInput schema / properties / websiteId / description
      Previous value: -"Organization-owned website id whose campaigns to list"New value: +"Website whose campaigns to list"
    • addedOutput schema / properties / campaigns / description
      Added value: +"Campaign identity only. Recipient lists, subjects, message content, user ids, organization ids and arbitrary metadata are excluded."
    • addedOutput schema / properties / page / description
      Added value: +"hasMore is true when more campaigns follow; pass nextCursor as cursor to get them"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely useful behavior: default page size, cursor pagination context, and the fact that sensitive fields (recipients, subject, content) are omitted from results.

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 tight sentences: the trigger first, then the returned shape and pagination, then the exclusion. Nothing is padded and each sentence carries distinct 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?

An output schema exists, so the return-shape sentence is a bonus rather than a necessity, and the pagination and exclusion notes complete the picture. Nothing an agent needs to invoke this list tool correctly is missing.

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%, and both limit and cursor are fully documented at 100% coverage, so the schema carries the parameter meaning. The description's mention of '20 per page by default' merely repeats the schema default and adds no format or usage syntax beyond it.

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 (list) and resource (email campaigns), scoped to a website. It also clarifies what is deliberately excluded from the payload (no recipients, subject or content), so an agent can tell it apart from anything that fetches full campaign detail.

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 trigger ('when someone asks which email campaigns one of their websites has') plus an exclusion ('Not for sending a campaign'). It stops short of naming the concrete alternative tool for sending, so it is clear but not fully routed.

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

All Supovia Customer Support 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