Skip to main content
Glama
Sign In

Infinite Audience

by io.github.no-fait
OverviewDiscussionsAdmin

List Campaigns

list_campaigns
Read-onlyIdempotent

List a page of campaigns for the organisation. Use when the user asks "what campaigns do I have?" or "show my active campaigns". Returns each campaign brief and status; use get_campaign for linked audience details. Pass the returned next_cursor as cursor to fetch another page. Requires 'discovery' scope.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum campaigns per page (default 10)
cursorNonext_cursor from a previous list_campaigns page
statusNoOptional filter by campaign status
compactNoReturn small name/status summaries by default; set false for each saved brief and timestamps. Call get_campaign for linked audiences.

Output Schema

NameRequiredDescriptionDefault
totalYes
guidanceNoInterpretation or recovery guidance for this result
campaignsYes
count_unitNo
page_countNoNumber of objects on this page, not the organization total
count_stateNoUnknown means no count; available does not guarantee freshness. Recount for a current value.
next_cursorYes
next_actionsNoSuggested next calls using returned IDs and available scopes. Not executed and not user consent.
money_displayNoCurrency amounts formatted once from source paths ending in _cents. Use verbatim; do not divide again. Null/missing source amounts are omitted, not zero.
population_inputNoPopulation input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": true,
+  "description": "Return small name/status summaries by default; set false for each saved brief and timestamps. Call get_campaign for linked audiences.",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum campaigns per page (default 25)"New value: +"Maximum campaigns per page (default 10)"
    • addedOutput schema / properties / count_state
      Added value: +{
+  "description": "Unknown means no count; available does not guarantee freshness. Recount for a current value.",
+  "enum": [
+    "unknown",
+    "available"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / count_unit
      Added value: +{
+  "const": "records",
+  "type": "string"
+}
    • addedOutput schema / properties / guidance
      Added value: +{
+  "description": "Interpretation or recovery guidance for this result",
+  "type": "string"
+}
    • addedOutput schema / properties / money_display
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Currency amounts formatted once from source paths ending in _cents. Use verbatim; do not divide again. Null/missing source amounts are omitted, not zero.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / next_actions
      Added value: +{
+  "description": "Suggested next calls using returned IDs and available scopes. Not executed and not user consent.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "arguments": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "tool": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tool",
+      "arguments",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / page_count
      Added value: +{
+  "description": "Number of objects on this page, not the organization total",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • addedOutput schema / properties / population_input
      Added value: +{
+  "additionalProperties": {},
+  "description": "Population input used for the preview; IDs refer to their current saved definitions",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds behavior they cannot express: what is returned per item (campaign brief and status), how pagination works ('pass the returned next_cursor as cursor'), and that a 'discovery' scope is required. It stops short of ordering guarantees or rate limits, which keeps it from a 5.

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?

Four short sentences, each doing distinct work: purpose, trigger examples, return shape, pagination, and auth. The primary capability is front-loaded before the sibling routing and pagination detail.

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?

For a paginated list tool with an output schema, an authorisation requirement, and a clear sibling, this covers everything an agent needs: what it returns, how to page, when to prefer get_campaign, and what scope is needed. Return-value specifics are correctly left to the output schema.

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, but the description adds a cross-field contract the schema cannot show: the output's next_cursor is the input for cursor to fetch another page. It also frames the status filter through the 'show my active campaigns' example, giving the enum a usage anchor.

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?

The opening sentence gives a specific verb ('List'), resource ('campaigns'), scope ('for the organisation'), and pagination semantics ('a page of'). It also distinguishes itself from get_campaign by name, so an agent can separate the two without opening either schema.

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?

It quotes concrete user utterances ("what campaigns do I have?", "show my active campaigns") that select this tool, and explicitly routes linked audience lookups to get_campaign as the alternative. The scope prerequisite ('discovery') is stated up front.

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

All Infinite Audience toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources