Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official
by brilliantdirectories
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

listUnsubscribes

Read-onlyIdempotent

Retrieve paginated unsubscribe records to audit email compliance and review opt-outs before launching campaigns.

Instructions

List unsubscribe records - Paginated enumeration of unsubscribe records. Read-only.

Use when: auditing the email unsubscribe list - useful for compliance (GDPR, CAN-SPAM) or before launching a new email campaign.

Pagination: cursor-based (limit, page). See Rule: Pagination for full cursor/cap/stop semantics.

Filter/sort: property+property_value+property_operator, order_column+order_type. See Rule: Filter operators for the verified-working operator set, silent-drop detection, and derived-field unfilterability.

See also: getUnsubscribe (single record by ID).

Returns: { status: "success", total, current_page, total_pages, next_page, prev_page, message: [...records] }. Each record is the full resource object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPagination cursor (use next_page from previous response)
limitNoRecords per page (default 25, max 100)
propertyNoColumn key to filter by (present on the response rows; a wrong name silently returns empty). For multi-condition AND, pass parallel arrays here and in `property_value`/`property_operator` — equal length, Nth entries paired. See Rule: Compound filters.
order_typeNoSort direction: ASC or DESC
order_columnNoColumn to sort by — a column key present on the response rows (a wrong name silently returns empty)
property_valueNoValue to filter by; array to pair with a `property` array (same length).
property_operatorNoFilter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. Array to pair with a `property` array (same length). See Rule: Filter operators for value shapes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.58.3
    • changedInput schema / properties / property_value / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "items": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "number"
-        }
-      ]
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    "type": "array"
+  }
+]
  2. Changed1 schema field changedv6.58.2
    • changedInput schema / properties / property_value / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "items": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    "type": "array"
+  }
+]
  3. Changed10 schema fields changedv6.58.0
    • changedInput schema / properties / order_column / description
      Previous value: -"Column to sort by"New value: +"Column to sort by — a column key present on the response rows (a wrong name silently returns empty)"
    • addedInput schema / properties / property / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / property / description
      Previous value: -"Field name to filter by"New value: +"Column key to filter by (present on the response rows; a wrong name silently returns empty). For multi-condition AND, pass parallel arrays here and in `property_value`/`property_operator` — equal length, Nth entries paired. See Rule: Compound filters."
    • removedInput schema / properties / property / type
      Removed value: -"string"
    • addedInput schema / properties / property_operator / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / property_operator / description
      Previous value: -"Filter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. See Rule: Filter operators for value shapes."New value: +"Filter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. Array to pair with a `property` array (same length). See Rule: Filter operators for value shapes."
    • removedInput schema / properties / property_operator / type
      Removed value: -"string"
    • addedInput schema / properties / property_value / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / property_value / description
      Previous value: -"Value to filter by"New value: +"Value to filter by; array to pair with a `property` array (same length)."
    • removedInput schema / properties / property_value / type
      Removed value: -"string"
  4. Addedv6.55.39
  5. Removedv6.55.19
  6. Addedv6.49.4
  7. Removedv6.48.1
  8. Addedv6.0.19
  9. Removedv6.0.18
  10. Addedv6.0.7
  11. Removed
  12. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses pagination behavior (cursor-based, limit/page), filter/sort nuances (silent-drop detection, operator semantics, derived-field unfilterability), and the return object structure. These go well beyond the annotations, which already indicate read-only, idempotent, and non-destructive behavior.

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 description is well-structured with clear sections: purpose, use when, pagination, filter/sort, see also, and returns. It is concise and front-loaded with the most important information.

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 read-only list tool with 7 optional parameters, the description covers pagination, filtering, sorting, and return structure. It mentions silent-drop and derived-field quirks. It could detail the record fields but states each record is the full resource object, which is acceptable given no 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?

The input schema has 100% coverage with detailed descriptions. The description adds value by explaining pagination cursor semantics, filter operator word forms, and silent-drop behavior. It references external rules but provides enough standalone context.

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 description clearly states that the tool lists unsubscribe records, is paginated, and is read-only. It distinguishes itself from the single-record retrieval tool 'getUnsubscribe' via the 'See also' section. The purpose is specific and unambiguous.

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?

The description provides explicit 'Use when' guidance for auditing, compliance, and campaign planning. It also points to the single-record alternative 'getUnsubscribe'. However, it does not explicitly exclude other list tools for different resources, but that is implicitly clear from the resource name.

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