Skip to main content
Glama
pushengage-mcp

pushengage-mcp

List subscriber attributes

pushengage_list_attributes
Read-only

Lists subscriber attributes for the current site so you can discover valid attribute keys before constructing an audience-group filter rule.

Instructions

Lists subscriber attributes (custom keys set on subscribers via the JS SDK) on the current site, paginated (response includes has_more). Use this to discover attribute key values before constructing an audience-group filter rule with field="attributes".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pushengage_list_attributes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed) for paginating beyond the first batch.
limitNoHow many attributes to return in this page. Min 1, max 100, default 10. To browse past the first 100, increase `page` instead of asking for a larger limit.
site_idNoOverride the currently selected site.
key_containsNoOptional substring filter on the attribute `key`. Maps to API `key_like`. Use this when looking up an attribute by name (e.g. searching for "plan" to find the "plan" attribute key).

Output Schema

NameRequiredDescriptionDefault
pageNo
limitNo
totalNo
has_moreNo
last_pageNo
attributesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_id / maximum
      Added value: +9007199254740991
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / attributes / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds behavior beyond that: results are paginated and the response carries `has_more`, and the listing is scoped to the current site. It omits rate limits and auth requirements, which keeps it short of 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?

Two sentences, zero waste, and the most decision-relevant information (what it lists and the scope) is front-loaded ahead of the pagination note and the downstream use case.

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 an output schema present, return values needn't be described, and the annotations carry the safety profile, so the remaining burden is purpose and routing — both handled well. The minor gap is that the optional `key_contains` lookup path and the create-vs-list boundary are left to the schema and sibling definitions.

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 `page`, `limit`, `site_id` and `key_contains` are all fully documented in the schema itself. The description's only parameter-adjacent contribution is the word "paginated", which the schema already explains in detail; it never mentions `key_contains` or the `site_id` override. Baseline 3 is appropriate.

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 specific verb and resource ("Lists subscriber attributes") and immediately defines what an attribute is ("custom keys set on subscribers via the JS SDK"), plus the scope ("on the current site"). An agent can distinguish this read/list tool from the sibling pushengage_create_attribute 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 Guidelines4/5

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

Gives an explicit, actionable when-to-use: discover attribute `key` values before building an audience-group filter rule with field="attributes". It does not name a when-not case or point at alternatives such as pushenge_create_attribute for creating new keys, but the positive routing is concrete rather than implied.

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