Skip to main content
Glama

get_email_performance

Read-onlyIdempotent

Read campaign delivery and engagement totals and comparison periods for the approved business.

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

Input Schema

NameRequiredDescriptionDefault
rangeNo30d

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds useful scoping context ("approved business") and hints at comparative output, but does not explain what a comparison period is, how it is chosen, or what metrics are included. That is a modest value-add beyond annotations, not a rich one.

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 no filler, and the read action is stated before the scoping qualifier. It is efficient, though the phrase "totals and comparison periods" is slightly compressed and could be clearer about what is returned.

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 tool with one optional enum parameter, rich annotations, and no output schema, the description is adequate but thin. It never clarifies what metrics constitute "delivery and engagement" or how the comparison period relates to the range parameter, which an agent would need to interpret results.

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?

There is a single optional parameter (range) with an enum and default, but schema description coverage is 0%, so the schema supplies only allowed values, not meaning. The description's mention of "comparison periods" loosely implies the range controls the comparison window, but it never explains how 30d/3m/12m affect the totals or the compared period, so it does not fully compensate for the coverage gap.

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 uses a specific verb ("Read") with a specific resource ("campaign delivery and engagement totals and comparison periods"), making the tool's output domain clear. It does not explicitly name a sibling to distinguish itself from list_email_campaign_runs or get_email_campaign_run, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "for the approved business" implies a scope constraint but gives no guidance on when to choose this tool over the campaign-run or email-settings siblings. There are no exclusions or preconditions stated, leaving the agent to infer usage from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources