Skip to main content
Glama

brevo_list_campaigns

Read-onlyIdempotent

Retrieve Brevo email campaigns with optional status filters and result limits to review sent, draft, or queued campaign activity.

Instructions

List Brevo email campaigns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>"
    },
    "name": "brevo_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCampaigns to return (max 100, default 25)
statusNoFilter by status (sent, draft, queued, ...)
api_keyYesBrevo API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no further behavioral context such as pagination, auth details, rate limits, or return shape, and merely restates the resource being listed.

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?

A single front-loaded sentence with zero wasted words. It is terse to the point of being under-specified, but structurally clean and concise.

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?

Given the simple three-parameter list operation, full schema coverage, and read-only annotations, the description is minimally sufficient. However, with no output schema, it provides no indication of what the response contains, and it offers no usage context for selecting this tool over alternatives.

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 description coverage is 100%, so the parameters (api_key, limit, status) are fully documented in the schema. The description adds no parameter semantics beyond the schema, which is the baseline case.

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?

States a clear verb and resource ("List Brevo email campaigns") that lets an agent identify the tool's core function. It does not explicitly differentiate from adjacent campaign-listing or Brevo contact tools, but the platform and resource are unambiguous.

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?

Provides no guidance on when to use this tool versus alternatives such as mailchimp_list_campaigns or brevo_list_contacts. The agent must infer usage solely from the tool name.

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

Deploy Server

Other Tools