NewsBreak Ads MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEWSBREAK_ACCESS_TOKEN | Yes | NewsBreak API access token. Can also be provided via --token command-line argument or .env file. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ad_accountsA | Get all ad accounts for specified organization IDs. This retrieves ad account IDs and names grouped by organization, filtered by user access permissions. |
| get_campaignsC | Get campaigns for an ad account with optional filtering. |
| get_tracking_eventsA | Get all tracking events for an ad account. Retrieves pixel and postback tracking events configured for the account. |
| run_performance_reportA | Run a synchronous performance report for campaigns, ad sets, or ads. This generates immediate reports on auction and reservation ads data. |
| get_campaign_summaryB | Get a quick summary of recent campaign performance. This is a convenience tool that fetches active campaigns and provides a high-level overview of account activity. |
| get_adsA | Get ads with complete creative asset details including images, videos, headlines, descriptions, and CTAs. This retrieves all ad information including the creative content (headlines, descriptions, call-to-action buttons, images/videos, landing page URLs, etc.) that users see. |
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 6 tools
Most tools are clearly distinct by resource: accounts, campaigns, ads, tracking events, and reports. However, get_campaign_summary overlaps somewhat with both get_campaigns and run_performance_report, so an agent may hesitate between the quick-summary and full-report options.
The naming convention is largely consistent with get_<resource> (get_ad_accounts, get_campaigns, get_ads, get_tracking_events). run_performance_report deviates from the get_ pattern, but it is still predictable and readable.
Six tools is a well-scoped count for an ads-focused server. Each tool addresses a meaningful part of the domain without unnecessary redundancy or feature bloat.
The read side is fairly complete, covering accounts, campaigns, ads, tracking events, and performance reporting. However, there are no mutation tools for managing campaigns or ads, and ad sets are referenced in reporting but have no direct retrieval tool, leaving potential gaps for a full ads workflow.