Postscript MCP Server and API by Cotlet

Create segment in Postscript

postscript_create_segment

Read-onlyIdempotent

Create segment in the user's own Postscript account from ChatGPT, Claude or any AI agent. Returns how to do it in Postscript step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Postscript Cloud Browser. Postscript's official API: Postscript has an API and an official MCP server, but neither builds or sends campaigns (checked 23 Oct 2026).

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": "postscript_create_segment"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds significant context beyond annotations: no side effects and no browser opened ('opens nothing by itself'), output is a procedural walkthrough, and the account is the user's own Postscript account. This also resolves the apparent conflict between the 'create' name and readOnlyHint=true, so an agent won't mistakenly assume state mutation occurs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the 'returns steps, opens nothing' caveat, then the execution path, then the API alternative. Mostly earns its sentences, though the 'ChatGPT, Claude or any AI agent' phrase and the dated verification note are slightly promotional padding.

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?

Complete enough for a guide-only tool with no params and no output schema: it says what comes back, that nothing is mutated, and which tools finish the job. The only gap is how to specify the segment parameters, which an agent must infer from the conversation.

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 tool takes zero parameters, so baseline is 4. The description does not explain how the target segment's details are conveyed (presumably from conversation context), which is the one thing an agent might puzzle over when calling a no-argument tool named 'create'.

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 (create a segment in the user's Postscript account) and immediately clarifies the actual delivered artifact: step-by-step instructions rather than the creation itself. This separates it cleanly from cotlet_app_guide (generic) and the cotlet_browser_* siblings, which it names as the follow-up execution path.

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?

Explicitly routes the agent: use this to learn the screens/buttons/fields, then execute with cotlet_browser_* in the Postscript Cloud Browser. It also preempts the obvious alternative (Postscript's API/official MCP server) with a dated check that those do not build or send campaigns. No explicit 'do not use when' clause, keeping it short of a 5.

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

All Postscript MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?