Skip to main content
Glama
Sign In
posterly-mcp-server

posterly-mcp-server

by awpthorp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_signup

Starts a 7-day free trial signup with Stripe Checkout and returns a signup poll URL plus browser handoff for password setup, so users can begin the posterly API add-on signup flow.

Instructions

Start the public posterly signup for a user before posterly API access exists. A new account starts a 7-day free trial: Stripe Checkout collects a card, nothing is charged today, and the card is charged on day 8 unless the paid plan starts sooner. API and MCP stay limited during the trial. The API add-on is still required. Returns a signup poll URL, a browser Checkout handoff URL, and a payment object for that Checkout session (trial length, whether anything is charged today, merchant, and agent-wallet instructions). An account that already had a trial is charged at checkout instead. The user still sets a password and approves social OAuth in the browser. Never ask for card numbers, a posterly password, or social passwords in chat.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional user or workspace name to pass into posterly signup.
tierNoposterly plan to start. Use starter unless the user explicitly chooses another plan.starter
debugNoWhen true, include the raw signup response JSON for debugging. Keep false for normal user-facing agent flows.
emailYesUser email address to sign up. Confirm this with the user before calling.
sourceNoSource label for analytics and support diagnostics.posterly_mcp_pre_auth_signup
intervalNoBilling interval. Public agent signup currently supports monthly billing.month
api_addonNoAlways true for AI agent setup because MCP/API access requires the API add-on.
return_pathNoWhere posterly should continue after checkout and password setup./dashboard/api?api_signup=success
tos_acceptedNoSet true only after the user has explicitly confirmed, in this conversation, that they accept the posterly terms at https://www.poster.ly/terms. Sending it here avoids a separate terms-confirmation step before client_secret is released.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.55.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes far beyond annotations: discloses the 7-day trial, day-8 charge, no charge today, repeat-trial accounts charged at checkout, limited API/MCP during trial, and the prohibition on collecting card/password/OAuth secrets in chat. That is rich operational and safety context not found in the annotations.

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 purpose then trial/charge behavior then return values, all substantive. Slightly dense with several clauses packed in, but nearly every sentence carries unique information.

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 mutation tool with open-world and no output schema, the description covers the billing flow, return shape, and follow-up browser steps. Minor gap: it doesn't say what to do if signup fails or how the poll URL should be used.

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 already 100%, so baseline is 3; the description adds value by explaining the return payload (poll URL, Checkout handoff URL, payment object) and the security rule around card/password data. It doesn't add per-parameter detail beyond schema, hence not a 5.

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 ('Start the public posterly signup') and disambiguates from sibling upgrade_subscription by scoping it to a user before API access exists. It also names get_signup_session implicitly via 'signup poll URL'.

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?

Clear context: use when the user has no account yet and needs a trial plus Checkout. It notes pre-auth state and that the API add-on is required, though it doesn't explicitly name get_signup_session or get_agent_signup_info as the follow-up alternative.

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

Deploy Server

Other Tools