Native MCP· Tool map

Native MCPFor AI assistants

Live

Native MCP tool map

Find the Native tool family for your task and use the authenticated server’s schemas for exact arguments.

This is a workflow map, not an exhaustive manifest. tools/list on your signed-in connection returns available tools with descriptions, JSON schemas and annotations. Follow every page of a paginated tool list. Only tools present on that connection can be called.

Account and brand context

#
TaskToolsIdentifiers
User and workspaceget_me, get_workspaces, get_workspaceReturned workspace id
Brandslist_brands, get_profileworkspaceId, then brandId
Voiceget_brand_voicebrandId
Productslist_products, get_product, list_product_imagesReturned product ids
Librarylist_brand_images, search_brand_library, get_imageReturned image ids

Social content

#
TaskTools
Plan and browseget_calendar, view_calendar, list_posts, view_post, view_posts
Generate draftscreate_draft, create_posts, get_post_batch_status
Edit copy and destinationsupdate_post, generate_caption, add_post_platforms, remove_post_platforms
Work with mediaupload_image, upload_video, attach_image_to_post, attach_video_to_post, replace_post_image, generate_image, regenerate_post_image, get_generation_job
Arrange slidesreorder_post_images, remove_post_image
Reviewapprove_post, reject_post, share_post_for_review, get_post_feedback
Publish and trackschedule_post, reschedule_posts, publish_post_now, get_post_status
Withdraw or removeunschedule_platform, move_platform_to_drafts, unpublish_post, delete_post
Connect social accountscreate_connect_link, disconnect_channel

Tool argument names differ. For example, view_post, approve_post and schedule_post take id; caption and image generation can take postId. A platformPostId identifies a particular destination of a post. Read the current schema rather than renaming one to another.

Meta ads, where enabled

#
TaskTools
Check setup and accountget_ads_overview, create_ads_connect_link
Generatecreate_ad, get_ad_status, generate_ad_batch, get_ad_pack_status
Choose inputslist_brand_assets, list_products, search_brand_library
Read and edit creativeslist_ads, get_ad_preview, update_ad_draft, regenerate_ad_image, add_ad_image, remove_ad_image, revert_ad_image, create_ad_renditions
Reviewapprove_ad, reject_ad
Configureupdate_ads_setup, create_campaign, create_ad_set, search_geo, estimate_reach, list_meta_pixels, get_meta_pixel_activity
Publishpublish_ad
Control deliverypause_ad, activate_ad, pause_ad_set, activate_ad_set, pause_campaign, activate_campaign, update_campaign_budget
Read performanceget_ad_insights, get_top_ads, get_ad_breakdowns, get_ad_metric_history, list_ad_set_ads

Social analytics

#

get_analytics_sync_status, refresh_analytics and get_post_analytics cover social metric freshness and performance. See Analytics before interpreting a comparison.

Call and result conventions

#

The Newsletter tool reference describes the 22 newsletter tools implemented in this release and awaiting public deployment: setup, Native mailing lists, contact imports, drafts, test emails, recipient snapshots, approval, sending and cancellation. They require brand-admin access. Use them only when advertised by the authenticated connector.

  • Use tools/call with the tool’s name and schema-valid arguments. A normal connector handles this protocol for the user.
  • Native success payloads are under structuredContent.data; the text content also carries the payload as JSON. Compatible clients may expose a parsed form.
  • Tool failures can return isError: true with { ok: false, error: { code, message, retryable } } inside the data payload. Input validation can instead produce a text error; authentication can fail before a tool runs.
  • Check explicit cancellation results such as { cancelled: true, changed: false }. Do not report them as completed changes.
  • Read annotations such as readOnlyHint as tool metadata. They are not substitutes for the user’s intent or the server’s permission checks.
  • Keep returned ids opaque. Respect pagination and output states. For writes with uncertain outcomes, read before retrying.

Outside this connector

#

Blog publishing requires a CMS integration; see Blog posts. Newsletter tools cannot bypass unavailable sending setup or enable recurring Autopilot. Partner onboarding and machine-to-machine access belong to the separate Native API preview.

Start with your Native account

Connect an assistant, choose your brand and ask for a first draft. Available tools follow your Native access.

Choose an assistant