Skip to main content
Glama
Sign In
Brevo MCP Server

Brevo MCP Server

by mark-o298
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_analytics_summary

Analyze campaign performance by retrieving a summary of analytics and insights for a chosen time period, with support for custom date ranges.

Instructions

Get comprehensive analytics summary with insights

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

Input Schema

NameRequiredDescriptionDefault
periodNoTime period for analyticslast7days
startDateNoCustom start date (required if period is "custom")
endDateNoCustom end date (required if period is "custom")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.7

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only says 'Get comprehensive analytics summary with insights', which does not reveal whether it is read-only, what data is fetched, or any side effects. Transparency is minimal.

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?

The description is a single concise sentence with no wasted words, though the phrase 'with insights' is somewhat redundant. It is appropriately front-loaded.

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

Completeness2/5

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

For a tool with 3 parameters and no output schema, the description does not explain what the summary contains, the output format, or how it differs from other analytics tools. This is insufficient for an agent to correctly select and invoke the 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 coverage is 100%, with all parameters having descriptions. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'get' and resource 'analytics summary', but it does not specify what type of analytics (campaign, contact, account) and does not distinguish from sibling tools like get_campaign_analytics or get_contact_analytics. The purpose is vague.

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?

No guidance is provided on when to use this tool versus the many sibling analytics tools, nor any conditional or contextual advice. The description lacks usage context.

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