Skip to main content
Glama

Postscript

by io.github.pipeworx-io

Postscript List Subscribers

postscript_list_subscribers
Read-onlyIdempotent

List SMS subscribers for a Postscript (Shopify) shop. Supports filtering by email, phone number, Shopify customer ID, and created/updated timestamps, plus sorting. Page-based pagination: returns { page_info: { page, total_pages }, subscribers: [...] }; pass page to walk results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-indexed page number (default 1). Walk until page === page_info.total_pages.
sortNoSort spec like "created_at__desc" or "updated_at__asc".
_apiKeyYesPostscript Private API token (Bearer). From Settings → API.
email__eqNoExact email match.
created_at__gteNoISO timestamp; subscribers created on/after this time.
created_at__lteNoISO timestamp; subscribers created on/before this time.
email__containsNoSubstring email match.
updated_at__gteNoISO timestamp; subscribers updated on/after this time.
phone_number__eqNoExact phone match (E.164, e.g. +15551234567).
phone_number__containsNoSubstring phone match.
shopify_customer_id__eqNoExact Shopify customer ID match.

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-postscript-api-key",
+    "page": 1,
+    "sort": "created_at__desc"
+  },
+  {
+    "_apiKey": "your-postscript-api-key",
+    "created_at__gte": "2024-01-01T00:00:00Z",
+    "phone_number__eq": "+15551234567"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds the pagination return format, which is useful context, but does not disclose rate limits or authentication details beyond schema.

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 with zero waste. The first sentence states the core purpose and supported filters; the second explains pagination mechanics. Every word earns its place.

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 tool with 11 parameters and no output schema, the description covers resource, filtering, sorting, and pagination adequately. It lacks error handling or edge-case details but is sufficient for common use.

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 parameters are well-described. The description adds meaning by explaining page-based pagination and sort pattern (e.g., 'created_at__desc'), which complements the schema without redundancy.

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 'List SMS subscribers for a Postscript (Shopify) shop,' specifying the verb and resource. It distinguishes from siblings like postscript_get_subscriber (single retrieval) and postscript_list_keywords (different resource).

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 explains filtering, sorting, and pagination usage ('pass page to walk results'). It implies when to use (listing vs single retrieval) but does not explicitly exclude alternatives or provide when-not scenarios.

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

All Postscript 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

A4/5.0
Disambiguation4/5

Most tools have clear, distinct purposes with detailed descriptions that differentiate them. However, there is some overlap among data query tools (e.g., ask_pipeworx, deep_research, entity_profile) and among Polymarket analysis tools, which could cause confusion for an agent.

Naming Consistency2/5

Tool names lack a consistent pattern, mixing snake_case (ai_visibility_check, bet_research) with descriptive phrases (ask_pipeworx, generate_llms_txt) and some with verbs (list_subscriptions, remember). This inconsistency makes it harder to predict tool names.

Tool Count3/5

With 34 tools, the server covers a broad scope including data querying, Polymarket analysis, SMS management, and utilities. While many tools are justified, the number feels slightly high and some tools (e.g., multiple Polymarket tools) might be consolidated.

Completeness4/5

The server provides comprehensive coverage for data analysis, entity resolution, fact-checking, and monitoring. However, SMS management lacks create/update operations for keywords and subscribers, and there is no tool for sending SMS messages, indicating minor gaps.

Resources