Skip to main content
Glama
dylancaponi

Agent Press Wire MCP Server

by dylancaponi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Write and distribute a press release over a newswire ($99 / $299)

distribute_press_release

Drafts and distributes AP-style press releases to 500+ news, TV and radio sites via newswire for press coverage. Quotes USDC price first, then charges after approval.

Instructions

Write a press release and distribute it over a newswire to get press coverage. PRICE: tier "wire" = $99 USDC (500+ news sites plus 100+ TV and radio network sites); tier "premium" = $299 USDC (everything in wire plus AP News, USA Today, Barchart, StreetInsider). Use when the user says things like "get press coverage", "write and distribute a press release", "send a press release to news sites", "put out a press release on the wire", "PR distribution". Drafts a 450-600 word AP-style release from the product URL; it goes through editorial review and is distributed, usually same day on weekdays. Returns an order_id; poll get_release_status for live links. Not accepted: crypto token sales, gambling, adult, health/cure claims, cannabis. Charges REAL USDC on Base mainnet from the user's own wallet (X402_PRIVATE_KEY) via x402. Two steps: call first WITHOUT confirm_token (or with quote_only=true) to get the price and a confirm_token; show the user the exact price and get explicit approval; then call again with identical parameters and that confirm_token (single use, expires in 10 minutes). It only pays if the price is <= MAX_SPEND_USD, the lifetime total stays <= MAX_TOTAL_SPEND_USD, and the server's payment terms match the pinned Agent Press Wire wallet and price; otherwise it returns the quote without paying. The service only settles payment if the job succeeds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity of the announcing company (newswire dateline).
tierYes"wire" = $99 (500+ news sites); "premium" = $299 (adds AP News, USA Today, Barchart, StreetInsider).
companyNoOptional company or project name.
countryYesCountry name, e.g. 'United States'.
quote_onlyNoIf true, never pay: just return the x402 price quote and a confirm_token. Use this first to show the user the price.
product_urlYesPublic URL of the product, launch page, or repo being announced.
announcementNoWhat is being announced (launch, new version, feature, funding, milestone). Strongly recommended: without it only news visible on the page is written about, and the call fails uncharged if there is none.
confirm_tokenNoconfirm_token from a previous quote of this tool with the exact same parameters, passed only after the user approved the quoted price. Without it the call only quotes.
contact_emailYesMedia contact email printed on the release (required by newswires).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (not read-only, open-world, non-idempotent); the description goes far beyond them by disclosing real USDC charging on Base mainnet, spend-limit gating, single-use/10-minute confirm_token expiry, editorial review and same-day weekday distribution, and that payment settles only on success.

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 and price, then usage triggers, then the payment protocol. Dense and mostly earned, but long enough that the tier pricing restates the enum and the not-accepted list competes with the critical confirm_token instructions for attention.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, non-idempotent, open-world tool with no output schema, it covers what the agent needs: the return value (order_id), how to get live links, the spend-safety gating, and the exact two-call protocol. Nothing material is missing.

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 baseline is 3, but the description adds workflow meaning not in the schema: confirm_token is single-use and expires in 10 minutes, quote_only exists to preview price, and the second call must repeat identical parameters. Tier pricing is duplicated from the schema, which limits it below 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+resource ('Write a press release and distribute it over a newswire') plus the concrete outcome (press coverage). It is clearly distinct from sibling get_release_status (polling) and announce_launch_newsroom, and the price tiers are surfaced up front.

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

Usage Guidelines5/5

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

Gives explicit trigger phrases ('get press coverage', 'PR distribution'), states the not-accepted categories, and spells out the mandatory two-step quote-then-confirm flow with the condition for using quote_only. It also names the follow-up tool for live links.

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