io.github.Synter-Media-AI/synter-ads
REMOTE · MCP.SYNTERMEDIA.AI · 2 COMPONENTS · SCANNED OCT 7
Reporting across 19 ad platforms, campaign creation on 14, write actions on 16, via AI.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.github.Synter-Media-AI/synter-ads MCP server?
io.github.Synter-Media-AI/synter-ads is a hosted endpoint at https://mcp.syntermedia.ai/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.syntermedia.ai
claude mcp add --transport http synter-media-ai-synter-ads 'https://mcp.syntermedia.ai/mcp/'
{
"mcpServers": {
"synter-media-ai-synter-ads": {
"url": "https://mcp.syntermedia.ai/mcp/"
}
}
} {
"servers": {
"synter-media-ai-synter-ads": {
"type": "http",
"url": "https://mcp.syntermedia.ai/mcp/"
}
}
} [mcp_servers.synter-media-ai-synter-ads] url = "https://mcp.syntermedia.ai/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"synter-media-ai-synter-ads": {
"type": "remote",
"url": "https://mcp.syntermedia.ai/mcp/",
"enabled": true
}
}
} openclaw mcp add synter-media-ai-synter-ads --url 'https://mcp.syntermedia.ai/mcp/' --transport streamable-http
mcp_servers:
synter-media-ai-synter-ads:
url: "https://mcp.syntermedia.ai/mcp/" {
"McpServers": {
"synter-media-ai-synter-ads": {
"Transport": "http",
"Url": "https://mcp.syntermedia.ai/mcp/"
}
}
} assistant mcp add synter-media-ai-synter-ads -t streamable-http -u 'https://mcp.syntermedia.ai/mcp/'
{
"mcpServers": {
"synter-media-ai-synter-ads": {
"type": "http",
"url": "https://mcp.syntermedia.ai/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Oct 26 −36
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://mcp.syntermedia.ai/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.syntermedia.ai | CN=YR1,O=Let's Encrypt,C=US | 23 Aug 2026 | 21 Nov 2026 | RSA 2048 | SHA256-RSA | 5dbc93cd9d736000581fea3bd7546081504 |
| SANs: mcp.syntermedia.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.syntermedia.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| syntermedia.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", resource_metadata="https://mcp.syntermedia.ai/.well-known/oauth-protected-resource", scope="tools:read tools:write"
Bearer error="invalid_token", resource_metadata="https://mcp.syntermedia.ai/.well-known/oauth-protected-resource", scope="tools:read tools:write" | Header | Value |
|---|---|
| www-authenticate | Bearer error="invalid_token", resource_metadata="https://mcp.syntermedia.ai/.well-known/oauth-protected-resource", scope="tools:read tools:write" |
Protected resource metadata
| Document | https://mcp.syntermedia.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.syntermedia.ai |
| Authorisation server | https://mcp.syntermedia.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.syntermedia.ai/mcp/ | Auth required | 401 | |
| http (plaintext) | http://mcp.syntermedia.ai/mcp/ | HTTPS enforced | 301 | https://mcp.syntermedia.ai/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
prospector_add_leads Prospector Add Leads ~324
Attach Priority/hand-picked leads to an existing Synter Prospector (EmailBison) campaign by numeric campaign_id. Accepts structured lead objects and/or CSV-shaped rows (email,first_name,last_name,company,title,linkedin_url,custom_shows) and an optional per-lead custom_variables list/object forwarded to EmailBison merge tokens (custom_shows becomes CUSTOM_SHOWS). IDEMPOTENT AND RESUMABLE: safe to re-run with the same leads — saves dedupe by email, the push reconciles against live campaign membership, and a re-run refreshes stale custom variables on already-attached leads instead of duplicating them. Work is time-budgeted: on a large cohort this returns complete=false with remaining_emails, and you should call it again with only those leads. Saves into the Prospector leads table then IcyPeas-verifies and gate-pushes via verify_and_push_leads. Defaults grade=A and outreach_tier=TIER_1 for Priority A cohorts; override per lead or via grade/outreach_tier args. Tenant-scoped like other prospector_* tools — unmapped orgs are refused. Does not launch the campaign. No live prod push without Growth GO. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| campaign_name | – | – | – |
| grade | string | – | – |
| leads | – | – | – |
| leads_csv | – | – | – |
| outreach_tier | string | – | – |
| tags | – | – | – |
No output schema declared.
No examples provided.
prospector_assign_inboxes_to_campaign Prospector Assign Inboxes To Campaign ~101
Attach explicitly selected sending inbox IDs to a Synter Prospector campaign. Requires a non-empty sender_email_ids array; never defaults to every inbox. Each ID must satisfy API-key inbox restrictions and the upstream authenticated sending workspace. Does not launch the campaign. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| sender_email_ids | array | yes | – |
No output schema declared.
No examples provided.
prospector_create_campaign Prospector Create Campaign ~172
Create a draft Synter Prospector outbound campaign with a sending schedule in the authenticated workspace. List campaigns first to avoid duplicates. Defaults to plain_text=true and open_tracking=false (tracking pixels and HTML wrappers depress deliverability on cold outbound); pass plain_text=false only when the sequence genuinely needs HTML. Change either later with prospector_update_campaign_settings. This does not launch or send. Add copy separately with prospector_update_campaign_sequence. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | – |
| name | string | yes | – |
| open_tracking | boolean | – | – |
| plain_text | boolean | – | – |
| send_weekends | boolean | – | – |
| start_time | string | – | – |
| timezone | string | – | – |
No output schema declared.
No examples provided.
prospector_create_reply Prospector Create Reply ~98
Approve and deliver an AI-drafted reply to an interested prospect lead. NOTE: on customer-workspace MCP connections this tool is not yet tenant-scoped and is refused rather than served from Synter's house tenant; use it from the Synter-internal surface. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| message | – | – | – |
| reply_id | string | yes | – |
No output schema declared.
No examples provided.
prospector_dedupe_leads Prospector Dedupe Leads ~108
Collapse duplicate Prospector lead rows (same email) into one record: keeps the campaign-linked / most complete row, fills its gaps from the duplicates, moves related records onto it, and deletes the duplicates. dry_run defaults to TRUE; pass dry_run=false to apply. Pass emails to target specific addresses. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | – |
| emails | – | – | – |
No output schema declared.
No examples provided.
prospector_get_analytics_summary Prospector Get Analytics Summary ~67
Get workspace-level Synter Prospector outbound analytics: campaign count, total replies, meetings booked, and per-campaign send/reply rates. Call this for an outbound reporting rollup across campaigns. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| days | – | – | – |
No output schema declared.
No examples provided.
prospector_get_bounced_leads Prospector Get Bounced Leads ~129
List bounced Prospector leads with a hard/soft/unknown split, the SMTP reason and code, the campaign, the sending inbox, and whether each address is already suppressed. Reads recorded bounces plus EmailBison's live bounced folder. Filter by campaign_id (numeric EmailBison id), since (ISO date), or bounce_type (hard/soft/unknown). [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| bounce_type | – | – | – |
| campaign_id | – | – | – |
| limit | integer | – | – |
| live | boolean | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
prospector_get_campaign Prospector Get Campaign ~73
Get a Prospector outbound campaign by ID. Numeric sending-platform IDs read live campaign configuration and sequence steps; Prospector UUIDs read the client-scoped database snapshot. Numeric live readback requires the updated Prospector backend. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
No output schema declared.
No examples provided.
prospector_get_campaign_performance Prospector Get Campaign Performance ~95
Get Synter Prospector outbound campaign performance: sends, opens, replies, meetings booked, and reply rate. Call this when reporting on an outbound sequence or comparing campaigns. Pass campaign_id for one campaign or omit it for the workspace rollup. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | – | – | – |
| days | – | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
prospector_get_campaigns Prospector Get Campaigns ~52
List Synter Prospector outbound campaigns with status, lead counts, replies, and schedule. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
prospector_get_inbox_health Prospector Get Inbox Health ~66
Get deliverability and warmup health for Prospector sending inboxes scoped to the authenticated owner. An empty result may indicate a missing owner-to-sending-domain mapping; it does not establish that reconnecting is necessary. [effect=read; scope=growth:read]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prospector_get_leads Prospector Get Leads ~126
List leads in the Prospector outbound pipeline, or filter by campaign, pipeline status, tag, or free-text search. campaign_id accepts the numeric EmailBison campaign id (resolved against live campaign membership) as well as the internal UUID. status filters the pipeline stage (e.g. new, contacted, replied, meeting_booked). search matches email, name, or company. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | – | – | – |
| limit | integer | – | – |
| search | – | – | – |
| status | – | – | – |
| tag | – | – | – |
No output schema declared.
No examples provided.
prospector_get_pipeline_summary Prospector Get Pipeline Summary ~49
Get high-level summary of Prospector outbound pipeline including leads, active campaigns, sent count, replies, meetings booked, and inbox health. [effect=read; scope=growth:read]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prospector_get_report Prospector Get Report ~63
Get one saved Synter Prospector outbound report by id, including the metrics payload used for campaign reporting. Call prospector_get_reports first when the report_id is unknown. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
prospector_get_reports Prospector Get Reports ~58
List saved Synter Prospector outbound reports (campaign, step, and analytics artifacts). Call this to find a report_id before prospector_get_report. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
prospector_get_step_performance Prospector Get Step Performance ~79
Get per-step performance for a Synter Prospector outbound sequence (sends, replies, and drop-off by email or LinkedIn step). Call this after prospector_get_campaign_performance when a campaign reply rate needs a step-level diagnosis. [effect=read; scope=growth:read]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
No output schema declared.
No examples provided.
prospector_reconcile_campaign_leads Prospector Reconcile Campaign Leads ~145
Reconcile a Prospector campaign's saved lead links with live EmailBison membership (numeric campaign_id): reports leads linked in Synter but not in EmailBison, EmailBison members not linked, and members with no saved lead, and returns the live member emails. dry_run defaults to TRUE; dry_run=false fixes the links in Synter only (never changes EmailBison). To detach invalid members use prospector_verify_leads then prospector_remove_leads. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| dry_run | boolean | – | – |
No output schema declared.
No examples provided.
prospector_remove_leads Prospector Remove Leads ~137
Detach leads from ONE Synter Prospector (EmailBison) campaign by numeric campaign_id. mode=stop (default) stops future emails and keeps history; mode=remove deletes them from the campaign (irreversible, resets that lead's campaign history). Does not suppress globally. Pass dry_run=true to preview. Never sends email. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| dry_run | boolean | – | – |
| emails | array | yes | – |
| mode | string | – | – |
| reason | string | yes | – |
No output schema declared.
No examples provided.
prospector_suppress_leads Prospector Suppress Leads ~173
Globally suppress email addresses in Synter Prospector: adds them to the suppression list every push gate reads, blocklists them in EmailBison and stops future emails in every campaign holding them. A reason containing 'bounce' also records a hard bounce. all_workspaces=true fans the EmailBison blocklist/stop out to every workspace. Global scope and all_workspaces are limited to the Synter house workspace; tenants use prospector_remove_leads. Pass dry_run=true to preview. Never sends email. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| all_workspaces | boolean | – | – |
| campaign_id | – | – | – |
| dry_run | boolean | – | – |
| emails | array | yes | – |
| reason | string | yes | – |
No output schema declared.
No examples provided.
prospector_update_campaign_sequence Prospector Update Campaign Sequence ~209
Write email sequence steps on a Synter Prospector campaign in the authenticated workspace. mode=append (default) adds sequence_steps after the existing steps. mode=edit rewrites existing steps in place, addressed by step_id (read step ids with prospector_get_campaign); ids, order, inboxes, and schedule are kept and it is safe on a live campaign. mode=delete removes the steps in delete_step_ids; steps that have already sent cannot be deleted. mode=replace swaps the whole sequence and is refused on an active campaign. Every non-append write is verified against a live readback. Use <br> line breaks and {FIRST_NAME}, {COMPANY}, {TITLE} tokens. This does not launch or send. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| delete_step_ids | – | – | – |
| mode | string | – | – |
| sequence_steps | – | – | – |
No output schema declared.
No examples provided.
prospector_update_campaign_settings Prospector Update Campaign Settings ~196
Update sending settings on an existing Synter Prospector campaign in the authenticated workspace: plain_text (send as plain text rather than HTML), open_tracking (tracking pixel), can_unsubscribe, max_emails_per_day, max_new_leads_per_day, sequence_prioritization. Only the arguments you pass are changed. This never launches, pauses, or otherwise changes campaign status — use prospector_update_campaign_status for that. Campaigns created before this tool existed default to plain_text=false; set plain_text=true to stop sending HTML-wrapped cold email. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| can_unsubscribe | – | – | – |
| max_emails_per_day | – | – | – |
| max_new_leads_per_day | – | – | – |
| open_tracking | – | – | – |
| plain_text | – | – | – |
| sequence_prioritization | – | – | – |
No output schema declared.
No examples provided.
prospector_update_campaign_status Prospector Update Campaign Status ~153
Pause, activate/resume, or archive a Prospector outbound campaign. Pass status=paused to stop sending, status=active (aliases: running, resume, launch, start, enabled) to call EmailBison launch_campaign, or status=archived to archive it (refused while active: pause first; history is kept). NOTE: on customer-workspace MCP connections this tool is not yet tenant-scoped and is refused rather than served from Synter's house tenant; use it from the Synter-internal surface. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| status | string | – | – |
No output schema declared.
No examples provided.
prospector_update_lead_custom_variables Prospector Update Lead Custom Variables ~156
Refresh EmailBison custom variables on leads ALREADY attached to a Synter Prospector campaign, without re-pushing them. Pass campaign_id plus leads=[{email, custom_variables}], where custom_variables is a list of {name, value} (names are uppercased by the backend, e.g. CUSTOM_SHOWS) or a plain {NAME: value} object. Idempotent: re-running overwrites the same variables. Use this when sequence merge tokens render blank or stale for leads that are already in the campaign. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| leads | array | yes | – |
No output schema declared.
No examples provided.
prospector_verify_and_push_leads Prospector Verify And Push Leads ~149
Lower-level lead attach: IcyPeas-verify already-saved Prospector leads and gate-push them into an existing EmailBison campaign by numeric campaign_id. Each lead needs email + grade (A/B/C/D) + outreach_tier (TIER_1/TIER_2/TIER_3/EXCLUDE). Prefer prospector_add_leads for CSV-shaped Growth cohorts that still need save_leads_to_database. Idempotent on email within the campaign. Tenant-scoped. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| leads | array | yes | – |
No output schema declared.
No examples provided.
prospector_verify_leads Prospector Verify Leads ~140
Verify-only email check for Prospector leads: IcyPeas-verifies each address and returns valid / invalid / risky / unknown with the raw status, plus whether it is suppressed. No campaign, no push, no company-name gate, no domain cooldown. persist=true (default) records the verdict on your saved leads so the push gate can use it. Time-budgeted: re-call with `remaining` until complete=true. Up to 200 emails per call. [effect=write; scope=growth:write; requires=prospectorAccess; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | – |
| persist | boolean | – | – |
No output schema declared.
No examples provided.
publish_gtm_container Publish GTM Container ~89
Publish a GTM container — creates a version from the default workspace and publishes it. PUSHES ALL WORKSPACE CHANGES LIVE to the site's tracking immediately. Approval-gated. [effect=publish; scope=tracking:write; requires=campaignPublishing; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| conflict_resolution | – | – | – |
| container_id | – | – | – |
| version_name | – | – | – |
No output schema declared.
No examples provided.
publish_landing_page Publish Landing Page ~87
Publish a landing page draft, making it live at syntermedia.ai/lp/{slug} (free). A page that lost its last benchmark_landing_page run is refused until fixed or acknowledged. [effect=publish; scope=landing_pages:publish; requires=campaignPublishing; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_benchmark | boolean | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
publish_organic_post Publish Organic Post ~76
Publish an approved, preflighted organic-post revision once to its exact bound destination. Requires separate publish approval and never automatically retries an ambiguous provider outcome. [effect=publish; scope=social:write; requires=campaignPublishing; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | – |
| revision_hash | string | yes | – |
No output schema declared.
No examples provided.
publish_plan_document Publish Plan Document ~103
Publish a campaign plan for review, generating a shareable URL. Moves the plan from building/draft to in_review; a reviewer approves it at share_url, then execute_campaign_plan launches it. Runs plan QA (incl. the live tracking preflight) and pins the scorecard to the document. [effect=publish; scope=workspace:write; requires=campaignPublishing; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| expected_version | – | – | – |
| plan_id | string | yes | – |
No output schema declared.
No examples provided.
publish_skill Publish Skill ~48
Create or update a private workspace skill from a complete SKILL.md document [effect=write; scope=skills:write]
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| skill_slug | string | yes | – |
No output schema declared.
No examples provided.
publish_to_github Publish To GitHub ~127
Publish a markdown blog post to a connected GitHub repo: commit <content_path>/<slug>.md and open a PR for the customer to review and merge (never pushes directly). Free. [effect=publish; scope=workspace:code; requires=campaignPublishing; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| base_branch | – | – | – |
| category | – | – | – |
| content_path | – | – | – |
| date | – | – | – |
| description | – | – | – |
| markdown | string | yes | – |
| open_pr | – | – | – |
| slug | string | yes | – |
| tags | – | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
pull_amazon_ads_performance Pull Amazon Ads Performance ~235
Get Amazon Ads (Sponsored Products/Brands/Display) metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Amazon reporting retains about 90 days, so windows are capped there. When counting 'live' campaigns, only count campaigns with state=ENABLED AND active ad groups with budget remaining — ARCHIVED campaigns are NOT active. IMPORTANT: If the user has multiple Amazon Ads accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| ad_type | string | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_amazon_dsp_performance Pull Amazon DSP Performance ~161
Pull Amazon DSP campaign performance data (2 credits) Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Amazon reporting retains about 90 days, so windows are capped there. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_cm360_performance Pull CM360 Performance ~161
Get Campaign Manager 360 (CM360) metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Use account_name to specify which account when multiple are connected. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_criteo_ads_performance Pull Criteo Ads Performance ~162
Get Criteo Commerce Media metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Returns displays, clicks, cost, conversions, and revenue per campaign. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_dv360_performance Pull DV360 Performance ~163
Get Display & Video 360 (DV360) metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Use account_name to specify which account when multiple are connected. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_freewheel_performance Pull FreeWheel Performance ~205
Get FreeWheel Buyer Cloud (Beeswax) metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for custom ranges, or days for a rolling window. Any window up to 3 years (1095 days) is accepted; long windows are fetched in platform-sized chunks and stitched, and `truncated`/`warnings` in the result say when a read was bounded. Use account_name to specify which account when multiple are connected. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_google_ads_performance Pull Google Ads Performance ~349
Get Google Ads campaign metrics — impressions, clicks, spend, conversions per campaign (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for custom ranges like weekends, or days for a rolling window. last_N_days presets cover the N complete days ending YESTERDAY (Google Ads semantics; use date_range=today for today). segment=date|week breaks metrics out per day or per week (one call for a pacing or creative-fatigue trend — don't loop one call per week). Paginate with limit/offset (next_offset in the result); at level=ads set include_ad_text=false to fit several hundred ads per page. Any window up to 3 years (1095 days) is accepted; long windows are fetched in platform-sized chunks and stitched, and `truncated`/`warnings` in the result say when a read was bounded. IMPORTANT: If the user has multiple Google Ads accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| include_ad_text | – | – | – |
| level | string | – | – |
| limit | – | – | – |
| offset | integer | – | – |
| segment | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_instacart_ads_performance Pull Instacart Ads Performance ~163
Get Instacart Ads metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Returns impressions, clicks, spend, attributed orders, and attributed sales per campaign. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_linkedin_ads_performance Pull LinkedIn Ads Performance ~251
Get LinkedIn Ads metrics — impressions, clicks, spend, conversions per campaign (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for custom ranges, or days for a rolling window. Any window up to 3 years (1095 days) is accepted; long windows are fetched in platform-sized chunks and stitched, and `truncated`/`warnings` in the result say when a read was bounded. Pass campaign_group_ids (comma-separated) to filter to specific campaign groups. IMPORTANT: If the user has multiple LinkedIn accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| campaign_group_ids | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_linkedin_company_engagement Pull LinkedIn Company Engagement ~99
Pull LinkedIn Ads Company Engagement report — shows which companies have seen your ads and how engaged they are (2 credits) [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| audience_id | – | – | – |
| country | – | – | – |
| days | integer | – | – |
| engagement_level | – | – | – |
| limit | integer | – | – |
| max_employees | – | – | – |
| min_employees | – | – | – |
No output schema declared.
No examples provided.
pull_meta_ads_performance Pull Meta Ads Performance ~239
Get Meta (Facebook/Instagram) Ads metrics — impressions, clicks, spend, conversions per campaign (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for custom ranges, or days for a rolling window. Any window up to 3 years (1095 days) is accepted; long windows are fetched in platform-sized chunks and stitched, and `truncated`/`warnings` in the result say when a read was bounded. IMPORTANT: If the user has multiple Meta Ads accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| level | string | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_microsoft_ads_performance Pull Microsoft Ads Performance ~232
Get Microsoft (Bing) Ads metrics — impressions, clicks, spend, conversions per campaign (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for custom ranges, or days for a rolling window. Any window up to 3 years (1095 days) is accepted; long windows are fetched in platform-sized chunks and stitched, and `truncated`/`warnings` in the result say when a read was bounded. IMPORTANT: If the user has multiple Microsoft Ads accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_openai_ads_performance Pull OpenAI Ads Performance ~231
Get OpenAI Ads metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Pulls insights from the OpenAI Ads API. Optional scope: campaign_id, ad_group_id, or ad_id to scope the report. Defaults to the selected scope's natural aggregation level; unscoped defaults to ad_account. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| ad_group_id | – | – | – |
| ad_id | – | – | – |
| aggregation_level | – | – | – |
| campaign_id | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| limit | integer | – | – |
| start_date | – | – | – |
| time_granularity | – | – | – |
No output schema declared.
No examples provided.
pull_pinterest_ads_performance Pull Pinterest Ads Performance ~182
Get Pinterest Ads metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. IMPORTANT: If the user has multiple Pinterest ad accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| level | string | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_reddit_ads_performance Pull Reddit Ads Performance ~228
Get Reddit Ads metrics — impressions, clicks, spend, conversions per campaign (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for custom ranges, or days for a rolling window. Any window up to 3 years (1095 days) is accepted; long windows are fetched in platform-sized chunks and stitched, and `truncated`/`warnings` in the result say when a read was bounded. IMPORTANT: If the user has multiple Reddit Ads accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_snap_ads_performance Pull Snap Ads Performance ~162
Get Snapchat Ads metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Use account_name to specify which account when multiple are connected. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| level | string | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_spotify_ads_performance Pull Spotify Ads Performance ~156
Get Spotify Ads metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Use account_name to specify which account when multiple are connected. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_target_roundel_performance Pull Target Roundel Performance ~161
Get Target Roundel retail media metrics (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for a fixed historical range, or days for a rolling window. Returns impressions, clicks, spend, conversions, and revenue per campaign. [effect=read; scope=campaigns:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
pull_tiktok_ads_performance Pull TikTok Ads Performance ~243
Get TikTok Ads metrics — impressions, clicks, spend, conversions per campaign (2 credits). Date window: date_range preset (today, yesterday, last_7_days, last_14_days, last_30_days, last_90_days, last_180_days, last_365_days, last_2_years, last_3_years), start_date/end_date (YYYY-MM-DD) for custom ranges, or days for a rolling window. Any window up to 3 years (1095 days) is accepted; long windows are fetched in platform-sized chunks and stitched, and `truncated`/`warnings` in the result say when a read was bounded. For detailed video engagement metrics use tiktok_ads_get_insights. IMPORTANT: If the user has multiple TikTok Ads accounts connected, you MUST ask which account to use BEFORE calling this tool — pass account_name to select it. [effect=read; scope=reporting:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| account_name | – | – | – |
| date_range | – | – | – |
| days | integer | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
What is the io.github.Synter-Media-AI/synter-ads MCP server?
io.github.Synter-Media-AI/synter-ads is an MCP server listed in the public MCP registry as io.github.Synter-Media-AI/synter-ads. Reporting across 19 ad platforms, campaign creation on 14, write actions on 16, via AI. This page covers its hosted endpoint (https://mcp.syntermedia.ai/mcp/).
Is the io.github.Synter-Media-AI/synter-ads MCP server safe to use?
io.github.Synter-Media-AI/synter-ads scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Synter-Media-AI/synter-ads MCP server expose?
io.github.Synter-Media-AI/synter-ads exposes 235 tools: get_organic_publishing_readiness, draft_organic_post, validate_organic_post, approve_organic_post, schedule_organic_post, and 230 more. Their descriptions and schemas cost roughly 25,044 tokens of context every time the server is loaded.
Does the io.github.Synter-Media-AI/synter-ads MCP server require authentication?
Yes. io.github.Synter-Media-AI/synter-ads asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.Synter-Media-AI/synter-ads MCP server still maintained?
io.github.Synter-Media-AI/synter-ads is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.