Skip to main content
Glama
pushengage-mcp

pushengage-mcp

List segments

pushengage_list_segments
Read-only

Lists PushEngage segments for the current site with pagination and optional name filtering, returning IDs, names, subscriber counts, status, and URL matching criteria.

Instructions

Lists segments on the current site, paginated (response includes has_more). Each item carries segment_id, name, current subscriber count, status, and any URL matching criteria.

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_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed) for paginating beyond the first batch. e.g. with limit=100 the second page (segments 101–200) is page=2.
limitNoHow many segments 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.
name_containsNoOptional case-insensitive substring filter on segment_name.

Output Schema

NameRequiredDescriptionDefault
pageNo
limitNo
totalNo
has_moreNo
segmentsNo
last_pageNo

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 / segments / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. First observedv0.1.0

TDQS

A3.8/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 safety is covered. The description adds genuinely new behavioral detail the annotations do not carry: results are paginated and the response exposes `has_more`, and each item includes subscriber counts and URL matching criteria. It omits anything about auth or rate limits, which keeps it below 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 compact sentences, front-loaded with the action and scope, followed by the pagination and item-shape facts. No filler or restated title material.

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?

For a read-only paginated list tool with a full input schema and an output schema that covers return values, the description supplies the operational facts an agent needs (pagination, has_more). The only meaningful gap is any guidance about when filtering by name_contains or overriding site_id is warranted.

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%, including page/limit interplay and the name_contains substring filter, so the schema does the heavy lifting. The description reinforces that pagination is in play via `has_more`, but adds no syntax or semantics beyond what the schema documents. Baseline 3 applies.

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?

States a specific verb and resource ("Lists segments") plus the scope ("on the current site"), which separates it from mutating siblings like create_segment or delete_notification. It does not explicitly name an alternative for filtered lookups, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the browse/list path for segment data, and the "current site" phrase hints that site scoping matters. There is no explicit when-to-use guidance, no mention of when to prefer a name-filtered lookup, and no note that site_id can override the selected site.

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