Skip to main content
Glama

Courier

by io.github.trycourier

update_audience

Idempotent

Create or update an audience with a filter definition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name
filterNoAudience membership filter. Either a single condition ({ operator, path, value }) or a group ({ operator: "AND" | "OR", filters: [...] }) nesting to any depth. Example: { "operator": "AND", "filters": [{ "operator": "EQ", "path": "title", "value": "Engineer" }, { "operator": "INCLUDES", "path": "tags", "value": "beta" }] }
audience_idYesThe audience ID
descriptionNoDescription

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / filter / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "description": "A single condition evaluated against one user profile field",
+    "properties": {
+      "operator": {
+        "description": "Comparison to apply, e.g. \"EQ\", \"INCLUDES\", \"IS_AFTER\"",
+        "enum": [
+          "ENDS_WITH",
+          "EQ",
+          "EXISTS",
+          "GT",
+          "GTE",
+          "INCLUDES",
+          "IS_AFTER",
+          "IS_BEFORE",
+          "LT",
+          "LTE",
+          "MEMBER_OF",
+          "NEQ",
+          "OMIT",
+          "STARTS_WITH"
+        ],
+        "type": "string"
+      },
+      "path": {
+        "description": "Dot-notation path into the user profile, e.g. \"title\" or \"location.city\"",
+        "type": "string"
+      },
+      "value": {
+        "description": "Value to compare against. Omit for existence checks like \"EXISTS\"",
+        "type": [
+          "string",
+          "number",
+          "boolean"
+        ]
+      }
+    },
+    "required": [
+      "operator",
+      "path"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "A group combining nested filters with AND/OR",
+    "properties": {
+      "filters": {
+        "description": "Conditions and/or nested groups to combine",
+        "items": {
+          "$ref": "#/properties/filter"
+        },
+        "type": "array"
+      },
+      "operator": {
+        "description": "How the nested filters combine. The combinator lives on the group itself",
+        "enum": [
+          "AND",
+          "OR"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "operator",
+      "filters"
+    ],
+    "type": "object"
+  }
+]
    • changedInput schema / properties / filter / description
      Previous value: -"Filter definition object (operator, rules)"New value: +"Audience membership filter. Either a single condition ({ operator, path, value }) or a group ({ operator: \"AND\" | \"OR\", filters: [...] }) nesting to any depth. Example: { \"operator\": \"AND\", \"filters\": [{ \"operator\": \"EQ\", \"path\": \"title\", \"value\": \"Engineer\" }, { \"operator\": \"INCLUDES\", \"path\": \"tags\", \"value\": \"beta\" }] }"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering the basic safety profile. The description adds a small amount beyond that by mentioning 'Create or update' (upsert behavior) and emphasizing the filter definition. It does not disclose side effects, whether existing filters are replaced or merged, or any permission requirements, but the annotation coverage lowers the burden.

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?

The description is one short, direct sentence with no filler. It front-loads the core action and resource. It earns its place, though it could carry a bit more useful context without becoming verbose.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema richly documents parameters and the filter grammar, so an agent can construct valid inputs. However, the description alone leaves ambiguity around create-versus-update behavior, return values (no output schema), and whether calling with only audience_id has meaningful side effects. These are notable gaps, but not fatal given schema and annotation coverage.

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 the schema already documents every parameter including the nested filter structure and example. The description's phrase 'filter definition' maps to the filter parameter but provides no additional semantic detail beyond what the schema already offers. Baseline 3 is appropriate.

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 names a specific action and resource: "Create or update an audience with a filter definition." It clearly distinguishes this from sibling tools like list_audiences, get_audience, and delete_audience. However, the dual verb 'Create or update' is slightly ambiguous against the tool name 'update_audience', though it may intentionally signal upsert semantics.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives, or whether it is preferred over get_audience/list_audiences for inspection tasks. It also does not state when an audience is created versus updated, despite saying 'Create or update.' The context must be inferred entirely from the tool name and schema.

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

All Courier toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation3/5

Tools are mostly organized as distinct resource/action pairs, but several clusters are easy to confuse: list subscription tools (add_subscribers_to_list vs bulk_subscribe_to_list vs subscribe_user_to_list), message vs message-content vs message-history retrieval, and the many journey/journey-template list/get tools. Detailed descriptions rescue most selections, but the sheer number of near-identical verb/resource names creates real misselection risk.

Naming Consistency4/5

Almost all tools follow a snake_case verb_noun pattern (create_, get_, list_, replace_, send_, publish_, archive_). Minor deviations keep it from a perfect score: courier_installation_guide is noun-first, and add_bulk_users sits awkwardly next to the bulk_add_* family, but the overall convention is predictable and readable.

Tool Count1/5

144 tools is an extreme working-set size for an agent to hold and choose from, far beyond the reasonable 3–15 range. Even for a broad platform like Courier, this should be split into focused sub-servers (templates, journeys, users, lists, preferences, etc.) to remain usable.

Completeness4/5

The surface is remarkably comprehensive, covering sending, templates, journeys, automations, users, tenants, lists, preferences, providers, routing, brands, audiences, translations, digests, bulk jobs, and audit events. Notable gaps exist—automation template CRUD and digest schedule management are missing—but most workflows can still be completed with workarounds.

Resources