Skip to main content
Glama

brevo_list_contacts

Read-onlyIdempotent

Retrieves Brevo contacts with pagination support, returning up to 1000 per request via your API key to support audience review and outreach workflows.

Instructions

List Brevo contacts.

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

Input Schema

NameRequiredDescriptionDefault
limitNoContacts to return (max 1000, default 50)
offsetNoPagination offset
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?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that — no note on pagination semantics, whether the default 50-cap silently truncates results, or any rate-limit/account-scope context, which are the behaviors an agent actually needs on a list endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words, zero waste, but also zero structure — nothing is front-loaded beyond the bare operation. It is concise to the point of being under-specified rather than efficiently structured.

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 simple read-only list tool, the schema plus annotations carry most of the load and there is no output schema to explain. However, the description leaves the agent without any statement of what the results represent (all contacts? account-scoped?) or whether truncation/paging matters, which is a meaningful gap for an enumeration tool.

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% and the schema already documents limit (max 1000, default 50), offset, and api_key. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 states a specific verb (List) and resource (Brevo contacts), so the operation is unambiguous. It does not name or differentiate itself from related siblings such as brevo_list_campaigns or hubspot_list_contacts/intercom_list_contacts, but the 'Brevo' qualifier in the name plus the plain resource noun make the target obvious.

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?

There is no guidance on when to use this versus alternatives, no mention of prerequisites (an API key is required), and no note that this is a paged enumeration rather than a filtered search. The agent must infer everything 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