Available Tools
Every tool the Netcore CE MCP server exposes to an AI assistant, grouped by domain, with its access level and inputs.
Overview
The Netcore CE MCP server includes 33 tools. 23 are read tools that help you search, view, and analyse campaign-related data without making any changes to your account. 10 are write tools that create or modify records, or send a test message.
| Access level | Tools | Availability |
|---|---|---|
| Read | 23 | Available on every account with MCP enabled |
| Write | 10 | Available only on accounts where an Admin has enabled write access |
Write tools are not offered to the assistant on read-only accounts, and are refused at call time if attempted. See Access from Netcore Panel for how to change this setting.
Write Tool Behaviour
Every write tool runs in two steps.
- The assistant calls the tool without confirmation. Nothing is created or changed. The tool returns a summary of exactly what it would do.
- You review that summary. If you approve it, the assistant calls the tool again with confirmation, and the change is applied.
App Push is the only writable channelCampaign creation, template creation, approval, and test sends exist for App Push and no other channel. Email, WhatsApp, RCS, and SMS are analytics only.
If you ask your assistant to create a campaign without naming a channel, by default, it creates an App Push campaign.
Cross-channel Campaigns
This is the starting point for most questions. Find the campaigns first, then pull their stats.
| Tool | Access | Description |
|---|---|---|
get_campaigns_list | Read | Compare delivery and performance metrics across Email, SMS, and WhatsApp for the campaigns you select, and quickly find the right campaigns using filters for channel, status, or date range |
Optional inputs: include_stats, include_revenue, page, limit, from_date, to_date, channel, status
Good to KnowSet
include_statsto fold performance metrics into the same rows, andinclude_revenueto fold in conversions and revenue. Results come back one page at a time, so a total across every campaign requires paging through all of them.
Channel-Specific Tools
Use these tools when you want to go deeper into a single campaign, review its full setup or check its performance for that channel.
App Push
The only channel that can be written to. Campaigns, templates, approvals, and test sends all live here.
| Tool | Access | Required inputs | Description |
|---|---|---|---|
get_apn_campaign_preview | Read | campaign_id | Review an app push campaign's setup, audience, content, and schedule in one place. |
get_apn_campaign_performance | Read | campaign_id | Check how an app push campaign performed by its published, sent, delivered, clicked, and failed counts. |
get_apn_campaign_failures | Read | campaign_id | Understand exactly why deliveries failed, with a detailed failure breakdown, a faster starting point than the funnel report. |
list_apn_templates | Read | None | Find push templates by name, ID, or platform. This is how a template name becomes a template ID. |
get_push_notification_template_content | Read | template_id | Read back everything saved on a single template so it can be shown or previewed. |
get_apps | Read | None | List the push apps on the account with their platform and app ID, needed to target a campaign or send a test message. |
create_apn_campaign | Write | template_id, app_ids, schedule_type | Build a push campaign end to end, covering audience, template, apps, schedule, expiry, and conversion goal. This is the only campaign creation tool on the server. |
update_apn_campaign | Write | campaign_id | Edit an existing push campaign. Narrow edits such as expiry or schedule do not require you to supply the rest of the campaign again. |
activate_campaign_and_make_live | Write | None | Approve a draft push campaign so it sends, moving it from Draft to Scheduled. |
save_and_create_apn_template | Write | title, message | Create a push content template, including background color or gradient, sticky, countdown timer, per platform overrides, and CTA buttons. |
update_apn_template | Write | template_id, title, message | Replace a template's content in full. |
send_test_message_before_launch | Write | campaign_id, tokens | Send a real test push to specific device tokens, using the campaign's own saved content. |
Important Point to Remember
- A campaign holds its own copy of the content it was built from. Updating a template changes the template only.
- To change what an existing campaign sends, update the campaign and point it at the template again.
Input for App Push Campaigns
The create_apn_campaign gathers five things before it can create anything:
| Input | Where it comes from |
|---|---|
| Audience | An existing segment found with list_segments, or a new one built with create_segment_from_filter_rules_with_NLP and saved with save_segment |
| Template | An existing template found with list_apn_templates, or a new one built with save_and_create_apn_template |
| App | An app_id from get_apps. The template's platform must match the apps the campaign targets. |
| Send time | Immediately, or a scheduled time in the future. There is no default. |
| Conversion tracking | The account's default goal, a specific event chosen with list_events, or none |
Email
Read-only analytics: performance, full campaign preview, and social engagement.
| Tool | Access | Required inputs | Description |
|---|---|---|---|
get_email_campaign_preview | Read | campaign_id | Review everything about an email campaign in one place including its setup, audience, content, and schedule. |
get_email_campaign_performance | Read | campaign_id | Check how an email campaign performed, from delivery through engagement. |
get_email_social_engagement | Read | campaign_id | See how an email campaign travelled beyond the inbox with social engagement counts. |
WhatsApp
| Tool | Access | Required inputs | Description |
|---|---|---|---|
get_whatsapp_campaign_preview | Read | campaign_id | Review a WhatsApp campaign's setup, audience, content, and schedule in one place. |
get_whatsapp_campaign_performance | Read | campaign_id | Check how a WhatsApp campaign performed, from delivery through engagement. |
RCS
| Tool | Access | Required inputs | Description |
|---|---|---|---|
get_rcs_campaign_preview | Read | campaign_id | Review an RCS campaign's setup, audience, content, and schedule in one place. |
get_rcs_campaign_performance | Read | campaign_id | Check how an RCS campaign performed, from delivery through engagement. |
SMS
| Tool | Access | Required inputs | Description |
|---|---|---|---|
get_sms_campaign_preview | Read | campaign_id | Review an SMS campaign's setup, audience, content, and schedule in one place. |
get_sms_campaign_performance | Read | campaign_id | Check how an SMS campaign performed, from delivery through engagement. |
Segments
Build an audience from a plain English description using the Segment Agent, then review and save it.
| Tool | Access | Required inputs | Description |
|---|---|---|---|
list_segments | Read | None | Find existing segments by name or ID, with audience counts and app push reachability. |
get_segment_status | Read | request_id | Pick up a segment build that is still processing. Long builds return a request ID so the conversation is not held up. |
create_segment_from_filter_rules_with_NLP | Write | message | Turn a plain English audience description into a segment through the Segment Agent. Returns a preview with audience count and push reachability. Nothing is saved at this stage. |
save_segment | Write | conversation_id | Save a segment after you have reviewed and approved its preview. Each call saves one segment. |
For more on the Segment Agent, see Create Segment with Co-Marketer.
Profile attributes
| Tool | Access | Required inputs | Description |
|---|---|---|---|
list_attributes | Read | None | List the contact profile fields on the account, such as FIRSTNAME or CITY, with their datatypes. Used for personalization tokens and segment rules. |
Contact lists
| Tool | Access | Required inputs | Description |
|---|---|---|---|
list_lists | Read | None | Find existing contact lists by name or ID. Their IDs also serve as a campaign's suppression lists. |
get_list_upload_status | Read | job_id | Check an import job for its state, file name, timestamps, and who started it. |
create_list | Write | name | Create an empty contact list. This is the first step of importing contacts. |
upload_contact_to_list | Write | list_id, file_url | Import contacts into an existing list from a downloadable CSV URL. Returns a job ID rather than a finished import. |
Events
| Tool | Access | Required inputs | Description |
|---|---|---|---|
list_events | Read | None | List the activities tracked on the account, flagged for whether each can serve as a campaign conversion goal. |
get_event_parameters | Read | event_id | List the payload fields of a single event, which can be used as conditions, which can carry revenue, and their permitted operators. |
Note
- All analytics tools enforce a maximum date range of 30 days per request.
- Supported status filters: Draft, Scheduled, Running, Paused, Completed, Suspended, Archived.
Limitations
- Date range: Analytics queries are limited to a maximum of 30 days per request.
- Batch size:
get_campaigns_listreturns up to 200 campaigns per page. Larger result sets are paged. - Content size: Email HTML content can be large (10–50 KB). Use
get_email_campaign_previewonly when you need to analyse the actual creative. - Channel availability: The MCP server only returns data for channels enabled on your workspace. Contact the Netcore helpdesk to enable additional channels.
- Campaign types: Only regular campaigns can be created or edited. Split and A/B campaigns are not supported.
Updated 1 day ago