Get Content Performance
get_content_performanceReports how content performed over a period, the numbers Performance › Social shows: performance.rows, one per pillar plus No pillar and Total, each with its posts in postRows. impressions and engagement are what each social post gained on days in the period, wherever it was published, so an older post still gaining counts (its postRows entry has publishedBeforeRange true); clicks are tracked-link clicks in the period. pageviews is a blog, FAQ or competitor page's views on the period's days, from the site tag in PostHog, from every country even with marketId, each day counted once it's over in the workspace time zone; 0 for social posts and without PostHog; a row whose posts are all social reads 0, which the app shows as n/a since social posts have no pageviews. posts counts posts published in the period, measured those with a gain dated in it, or for a website post Search numbers or a pageview day in it; an older website post with pageviews in the period is listed with publishedBeforeRange true. performance.daily is every day of the period with the impressions and engagement social posts gained on it, 0 on a day with none (blog Search numbers are only in the rows). previous has each row's impressions, engagement, clicks and pageviews, and its daily, for the same number of days just before. Mark reads a post daily to day 30, then weekly to day 90, and spreads a gain evenly over the days between readings; posts read only at day 1 and day 7 show nothing after day 7. A blog or other website post's impressions and clicks are Google Search's for its page in the period, from Search Console (with marketId, only searches from that market's country when it is an ISO code, as get_performance_overview and Performance › Search filter), with no engagement; KPI actuals leave them and pageviews out. kpis is the Targets page (/targets): every KPI target with its month (YYYY-MM), target, actual and progressPercent, computed the same way the page does. Impressions and engagement_rate actuals are what social posts gained on days in the target's month, wherever they were published, the same as performance for that month without blog Search numbers; posts_per_week counts posts published in it and leads those created in it; all in the workspace time zone; it ignores from, to, pillarId and marketId. period is past, current (actual so far) or not_started (actual null). When there is no number, actual is { note } with the reason, such as a metric Mark doesn't track yet. engagement_rate values are percents (4.5 means 4.5%). Does not change anything. Related: save_strategy_item (kind kpi_target), delete_strategy_item, get_search_performance, get_calendar, search_posts.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_content_performance"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Range end YYYY-MM-DD. | |
| from | No | Range start YYYY-MM-DD. Defaults to the last 28 settled days. | |
| marketId | No | Filter to one market's posts; website posts' Search numbers filter to its country. | |
| pillarId | No | Filter to one pillar. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kpis | Yes | ||
| appUrl | Yes | ||
| previous | Yes | ||
| performance | Yes |