Skip to main content
Glama
adpilot-mcp

adpilot-mcp

Official
by sholaxai

campaign_performance

Read-only

Retrieve campaign KPIs—spend, CTR, CPC, CPA, ROAS, and CPM—over the last N days, ranked by ROAS to compare performance and guide budget decisions.

Instructions

KPIs (spend, CTR, CPC, CPA, ROAS, CPM) per campaign over the last N days, ranked by ROAS.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile, and the description adds useful context about the metric set and ROAS-based ordering. It does not state pagination behavior, rate limits, or exact response structure, but those gaps are less critical for a simple read-only report.

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 definition is a single front-loaded sentence that names the metrics, grouping, time window, and ordering. Every element earns its place with no redundant wording.

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?

For a simple one-parameter read-only reporting tool with no output schema, the description is largely complete because it explains what is returned and how it is ranked. A minor gap is that it does not mention the default time window or response shape beyond the metric list.

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?

The description clarifies the single days parameter as 'last N days', which is helpful because the schema provides no description and 0% coverage. However, it omits the default value of 14 and the 1–90 range that the schema enforces, so it only partially compensates for the low schema documentation.

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 identifies a reporting resource: KPIs per campaign over a time window, ranked by ROAS. It lists the specific metrics returned, making the tool distinguishable from budget or status siblings, though it does not explicitly name when to choose it over those siblings.

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 is implied by the KPI-reporting language and the ROAS ranking, but there is no explicit when-to-use guidance or reference to alternatives such as list_campaigns or detect_anomalies. The agent must infer that this is the reporting tool.

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