Skip to main content
Glama

growthintel-mcp

Campaign Performance Tool

campaign-performance-tool
Read-onlyIdempotent

Returns the authenticated tenant's campaign performance, aggregated per campaign over a date window (default: last 30 days). Each row: campaign_name, channel, spend, leads, conversions, clicks, impressions, cost_per_lead. No PII — campaign-level totals only.

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": "campaign-performance-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of campaigns to return, ranked by spend.
date_toNoEnd date (YYYY-MM-DD). Defaults to today.
date_fromNoStart date (YYYY-MM-DD). Defaults to 30 days before date_to.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds genuinely new context not in the annotations: tenant scoping, campaign-level aggregation with no PII, the default 30-day window, and the exact row shape. It does not say what happens when 'limit' truncates a larger result set or how an empty date range is returned.

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?

Three compact sentences, front-loaded with the verb and grain, then the row shape, then the privacy note. Every element is informative, though 'No PII — campaign-level totals only' partly restates the aggregation grain already stated in the first sentence.

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?

With no output schema, the description compensates by enumerating the returned fields and the default time window, which is the essential information for interpreting results. Remaining minor gaps are truncation semantics for 'limit' and empty-result behavior for a read-only, three-parameter 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%, so all three parameters (limit, date_to, date_from) are already documented with defaults, including that ranking is by spend. The description only restates the default window at a high level and adds no format, boundary, or interaction detail beyond the schema, so 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?

States a specific verb and resource ('Returns the authenticated tenant's campaign performance') plus the aggregation grain ('per campaign over a date window'), which lets an agent distinguish it from a per-creative or pipeline-level view. It stops short of explicitly naming the near sibling 'creative-performance-tool', so the campaign-vs-creative distinction must be inferred from the grain statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage context is implied by the stated grain and default window (last 30 days), so an agent can tell it is a campaign-level aggregate report. However, there is no explicit when-to-use/when-not guidance and no pointer to the sibling tools that cover creative-level performance or pipeline overview, leaving the choice between them to inference.

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