postscript_list_keywordsList all active SMS keywords for the shop. Keywords are the text-to-join words (e.g. "JOIN") subscribers text to opt in. Returns keyword IDs, the keyword text, and associated subscription settings.
| Name | Required | Description | Default |
|---|---|---|---|
| _apiKey | Yes | Postscript Private API token (Bearer). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "_apiKey": "your-postscript-api-key"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds meaningful context: explains what keywords are and what the tool returns (IDs, text, subscription settings). No contradictions. Missing potential information about pagination or limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise and efficient: 27 words in two sentences. First sentence states action, second explains keywords and return value. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given rich annotations and simple parameter, the description covers the tool's purpose and output. Could mention if pagination exists or if the list is exhaustive, but overall sufficient for a listing tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema description already clarifies the _apiKey parameter. The tool description adds no additional meaning or context beyond what is in the input schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action (List) and resource (active SMS keywords for the shop), explains what keywords are, and specifies the return data (keyword IDs, text, settings). It distinguishes from sibling tools like postscript_get_keyword by implying a list vs singular retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives like postscript_get_keyword. The description implies it's for listing all active keywords, but does not exclude single keyword retrieval or provide usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.