Skip to main content
Glama

get_campaign_analytics

Read-onlyIdempotent

Retrieve historical push campaign metrics—sent, clicks, CTR, credits—and active scheduled queue items to audit performance or find scheduled campaign IDs.

Instructions

Retrieve historical push campaign delivery metrics (sent count, click count, CTR percentage, credits spent) and active scheduled queue items. Use this tool to audit campaign performance or find scheduled campaign IDs (cmp_sch_xxxx); do not use it to check QRIS payment invoices (use check_billing_and_qris_status instead) or raw subscriber device lists (use list_subscribers instead). Read-only operation requiring PUSHNOTIF_API_KEY with 0 credit cost. Returns JSON { summary: { total_sent, total_clicks, avg_ctr_percent }, campaigns: [{ id, app_id, title, delivered_count, click_count, ctr_percent, created_at }], scheduled_queue: [...] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of recent campaigns to return (1 to 50, default: 10)
app_idNoOptional application ID filter (format app_xxxx); omit to aggregate across all apps in the workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.2
    • changedInput schema / properties / app_id / description
      Previous value: -"Opsional: filter untuk App ID tertentu"New value: +"Optional application ID filter (format app_xxxx); omit to aggregate across all apps in the workspace"
    • changedInput schema / properties / limit / description
      Previous value: -"Jumlah riwayat kampanye terakhir yang ditampilkan (default: 10)"New value: +"Maximum number of recent campaigns to return (1 to 50, default: 10)"
  2. First observedv2.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, but the description adds non-obvious context: the required PUSHNOTIF_API_KEY and the fact that the call costs 0 credits. It also discloses the exact return shape, which annotations cannot convey.

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?

Three sentences, front-loaded with purpose then routing then operational facts, with zero filler. The inline JSON return spec earns its length because no output schema exists.

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

Completeness5/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 correctly supplies the return structure (summary/campaigns/scheduled_queue) plus auth and cost constraints. An agent has everything needed to call and interpret this 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% and both parameters (limit range/default, app_id format) are fully documented in the schema. The description adds no parameter-level syntax or semantics beyond that, so the baseline 3 applies.

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

Purpose5/5

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

Specific verb+resource with the exact metrics enumerated (sent count, click count, CTR, credits spent, scheduled queue). It also names the sibling alternatives it must not be confused with, so an agent can discriminate without opening schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use ('audit campaign performance or find scheduled campaign IDs') and when-not-to-use with two named alternatives (check_billing_and_qris_status, list_subscribers). Nothing is left to inference.

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