pressadvantage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRESS_ADVANTAGE_API_KEY | Yes | Your Press Advantage API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_organizationsA | List all organizations in the account |
| get_organizationA | Get details of a single organization by ID |
| create_organizationC | Create a new organization |
| update_organizationC | Update an existing organization |
| list_organization_releasesA | List all releases belonging to a specific organization |
| list_releasesA | List all press releases in the account |
| get_releaseA | Get details and current state of a single press release |
| create_releaseA | Create a self-written press release. The customer provides the full content. Use order_written_release instead if you want Press Advantage writers to write it. |
| order_written_releaseA | Order a professionally written press release. Press Advantage writers will create the content based on your brief. |
| revise_releaseB | Submit revised content for a release that needs content revision |
| approve_releaseA | Approve the content of a release that is waiting for customer approval. Optionally include edited content. |
| reject_release_to_writersB | Reject the release content and send it back to writers with revision instructions |
| cancel_releaseB | Cancel a press release order |
| finalize_draft_releaseB | Convert a draft release into an active order, submitting it for processing |
| get_release_pickup_urlsA | Get the list of pickup URLs showing where this release was published across news outlets. Only available once the release is in 'completed' state. |
| list_distributionsA | List available distribution add-on channels for a release. Use the returned IDs with add_distribution_upgrade to add channels. |
| add_distribution_upgradeB | Add a specific distribution channel (wire) to an existing release |
| upgrade_to_premiumB | Upgrade an existing release to premium distribution, adding Yahoo Finance and other premium outlets |
| list_pixelsA | List all retargeting pixels in the account |
| get_pixelA | Get details of a single retargeting pixel |
| create_pixelA | Create a new retargeting pixel to attach to press releases |
| update_pixelA | Update an existing retargeting pixel |
| list_scheduled_ordersA | List all scheduled release orders in the account |
| get_scheduled_orderA | Get details of a single scheduled release order |
| create_scheduled_orderA | Create a new scheduled release order that automatically generates recurring press releases |
| update_scheduled_orderB | Update an existing scheduled release order |
| add_scheduled_videoA | Attach a video to a scheduled release order |
| add_scheduled_imageA | Attach an image to a scheduled release order |
| add_scheduled_subjectA | Add a subject/topic to a scheduled release order |
| add_scheduled_keywordC | Add a keyword to a scheduled release order |
| add_first_release_keywordA | Add a keyword specifically for the first release in a scheduled order |
| sandbox_editor_rejectsA | [SANDBOX/TESTING ONLY] Simulate an editor rejecting the release content back to the customer for revision |
| sandbox_editor_approvesA | [SANDBOX/TESTING ONLY] Simulate an editor approving the release content |
| sandbox_distribution_orderedA | [SANDBOX/TESTING ONLY] Simulate distribution being ordered / triggered |
| sandbox_distribution_completedA | [SANDBOX/TESTING ONLY] Simulate distribution completing — release moves to 'completed' state |
| sandbox_approve_with_exceptionB | [SANDBOX/TESTING ONLY] Simulate an editor approving an order that has a guideline exception |
| sandbox_writers_deliverA | [SANDBOX/TESTING ONLY] Simulate writers delivering content for a written-for-you release |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 37 tools
Most tools are clearly separated by resource and action, such as releases, scheduled orders, organizations, and pixels. Potential overlaps like create_release vs order_written_release are explicitly distinguished, and sandbox tools are clearly labeled as testing-only. The main challenge is the sheer number of options, but each has a distinct purpose.
The naming pattern is mostly verb_noun (list_releases, create_organization, update_pixel), but there are notable deviations. For example, sandbox_editor_rejects and sandbox_editor_approves use a noun-verb structure while sandbox_approve_with_exception uses a verb-first structure, and add_first_release_keyword is a verbose variant of add_scheduled_keyword. This mixed style is still readable but not fully consistent.
With 37 tools, the server has an excessive number for a single domain, exceeding the typical well-scoped range of 3-15 tools. The 5 sandbox simulation tools add bulk and are only for testing, further inflating the count. This makes the tool surface feel heavy and difficult for agents to navigate efficiently.
The toolset provides extensive coverage of press release management: full lifecycle for releases (create, get, approve, reject, revise, cancel, finalize), scheduled orders, organization management, pixels, distribution upgrades, and pickup URLs. Minor gaps include missing delete operations for scheduled orders and releases (though cancel exists), but the core workflows are solid.