Skip to main content
Glama
kaminari-ad

@kaminari-ad/mcp

Official
by kaminari-ad
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

List Alerts

list_alerts
Read-onlyIdempotent

Fetch violation alerts with offer URL, country, status, matched rule type, and value. Filter by campaign, status, policy set, tag, country, or date range to pinpoint compliance issues.

Instructions

List violation alerts (one per scan + violating rule combo) with offer URL, country, status, scan back-reference, and the kind-aware fields rule_type (tag / iab_v3 / brand / ai_category / custom_taxonomy) + matched_value (the canonical text the scan matched against). Filter by campaign, status, policy set, tag, country and creation-date range; policy_set_id, tag and country_code take comma-separated values and match any of them. Pass the same filters to get_alert_stats to get counts that agree with this list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoComma-separated tag slugs. Matches alerts carrying any of them; see `list_tags`.
pageNo1-indexed page number.
limitNoPage size.
statusNoFilter by alert status. Open = unhandled; escalated = flagged for attention; resolved = closed; dismissed = closed without action.
date_toNoISO date (YYYY-MM-DD), inclusive upper bound on alert creation.
timezoneNoIANA timezone (e.g. 'Europe/Berlin') the date bounds are read in. Defaults to UTC. Omitting both dates spans all time.
date_fromNoISO date (YYYY-MM-DD), inclusive lower bound on alert creation.
campaign_idNoFilter to one campaign's alerts.
country_codeNoComma-separated ISO 3166-1 alpha-2 country codes, e.g. US,DE,JP.
policy_set_idNoComma-separated policy-set UUIDs. Matches alerts raised by any of them; see `list_policy_sets`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.14.0
    • addedInput schema / properties / country_code
      Added value: +{
+  "description": "Comma-separated ISO 3166-1 alpha-2 country codes, e.g. US,DE,JP.",
+  "type": "string"
+}
    • addedInput schema / properties / date_from
      Added value: +{
+  "description": "ISO date (YYYY-MM-DD), inclusive lower bound on alert creation.",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / date_to
      Added value: +{
+  "description": "ISO date (YYYY-MM-DD), inclusive upper bound on alert creation.",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / policy_set_id
      Added value: +{
+  "description": "Comma-separated policy-set UUIDs. Matches alerts raised by any of them; see `list_policy_sets`.",
+  "type": "string"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Comma-separated tag slugs. Matches alerts carrying any of them; see `list_tags`.",
+  "type": "string"
+}
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA timezone (e.g. 'Europe/Berlin') the date bounds are read in. Defaults to UTC. Omitting both dates spans all time.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.5.1
    • changedInput schema / properties / status / description
      Previous value: -"Filter by alert status. Open = unhandled; acknowledged = seen by an operator; resolved = closed; dismissed = closed without action."New value: +"Filter by alert status. Open = unhandled; escalated = flagged for attention; resolved = closed; dismissed = closed without action."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "open",
-  "acknowledged",
-  "resolved",
-  "dismissed"
-]New value: +[
+  "open",
+  "escalated",
+  "resolved",
+  "dismissed"
+]
  3. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / status / description
      Previous value: -"Filter by alert status."New value: +"Filter by alert status. Open = unhandled; acknowledged = seen by an operator; resolved = closed; dismissed = closed without action."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "open",
-  "ack",
-  "resolved",
-  "ignored"
-]New value: +[
+  "open",
+  "acknowledged",
+  "resolved",
+  "dismissed"
+]
  4. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), which aligns with the non-mutating 'List' verb. The description adds value beyond annotations by disclosing the dedup rule, the kind-aware rule_type values, and the filter behavior. No contradiction; annotation_contradiction=false.

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?

One information-dense sentence delivers the return fields, dedup rule, filter list, OR-match semantics, and the stats relationship with no filler. It is front-loaded with the return semantics. It is dense enough that a line break or two would aid readability, but nothing is wasted.

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 correctly carries the return-value burden by enumerating the fields (offer URL, country, status, scan back-reference, rule_type, matched_value) and the dedup semantics. Filters and pagination are covered by a fully-documented schema. Together they give an agent everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 because the schema already documents all 10 parameters with defaults and enum meanings. The description earns a 4 by adding semantics beyond the schema: the dedup definition, the kind-aware field context, and the OR-match behavior for comma-separated values. It also points out the cross-tool filter relationship with get_alert_stats.

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?

States a precise verb+resource ('List violation alerts') and enriches it with the dedup semantics ('one per scan + violating rule combo') and the exact returned fields (offer URL, country, status, scan back-reference, rule_type, matched_value). This distinguishes it clearly from the sibling get_alert_stats, which is about aggregates rather than the alert list itself.

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?

Gives clear actionable context: it explains that the same filters passed to get_alert_stats yield agreeing counts, which routes the agent between list vs. stats tools. It also explains the OR-match semantics of comma-separated filters. It stops short of an explicit 'use X instead when…' exclusion, which keeps it from a 5.

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

Deploy Server

Other Tools