Skip to main content
Glama

Nevent MCP

by io.github.nevent-dev

nevent_campaign_report

Read-only

Generate a comprehensive analytics report for a single campaign. Executes 13 parallel queries in one call returning opens, clicks, bounces, unsubscribes, conversions, revenue, and other key performance metrics. Use nevent_list_campaigns to get valid campaign IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeRangeNoOptional time range to restrict report data. Defaults to full campaign lifetime.
campaignIdYesCampaign ID to generate the analytics report for

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context beyond that: it executes 13 parallel queries in one call and returns a specified list of metrics, which helps the agent understand cost, scope, and output shape. It does not cover response structure or rate limits, but the annotations cover the safety profile.

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?

The description is two concise sentences, front-loaded with the action and scope. The performance note (13 parallel queries) and the ID prerequisite are efficient additions without fluff. Every sentence earns its place.

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

Completeness4/5

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

Given no output schema, the description lists the primary returned metrics and notes there are additional 'other key performance metrics.' It covers the essential return categories, the single-campaign scope, and the ID source. The vague 'other key performance metrics' leaves some ambiguity, but for an analytics report tool this is reasonably complete.

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%: campaignId and timeRange are already documented, including the default behavior of timeRange. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 clearly states a specific verb ('Generate') and resource ('a comprehensive analytics report for a single campaign'), and enumerates the main metrics returned. It does not explicitly distinguish itself from similar report/insights siblings like nevent_get_campaign_metrics or nevent_get_campaign_insights, so it falls short of a 5.

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?

The description provides clear context: use it for a single campaign report and use nevent_list_campaigns to obtain valid campaign IDs. It does not state when not to use it or name alternatives, but the single-campaign scope and prerequisite are clear.

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

All Nevent MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most domain groups are distinct, but the campaign reporting cluster has three tools returning overlapping engagement metrics (get_campaign, get_campaign_metrics, campaign_report), and paid_ads_status vs paid_ads_health have fuzzy boundaries. The detailed descriptions mitigate but do not eliminate the risk of an agent calling the wrong tool.

Naming Consistency3/5

All names use the nevent_ prefix and snake_case, and most CRUD operations follow verb_noun. However, several tools reverse the order or drop the verb entirely (segment_preview, segment_execute, campaign_report, paid_ads_status, analytics_query), making the convention mixed but still readable.

Tool Count1/5

With 59 tools, this is far above the 25+ 'too many' threshold and falls into the 50+ extreme range. The broad domain coverage explains some of the size, but for an agent the set is likely to be overwhelming and harder to navigate than a more focused server.

Completeness3/5

The core marketing workflow (segments, templates, campaign creation, quote, schedule, metrics) is covered, but there is no way to update, cancel, or delete a campaign, and templates and segments lack delete operations. These are notable lifecycle gaps that agents will hit when users want to change or clean up resources.

Resources