@prc/analytics registers two WordPress Abilities for traffic analysis. Both are read-only and exposed as MCP public tools.
Ability index
| Ability | Permission | Side effects |
|---|---|---|
prc-analytics/analyze-post | manage_options (via with_site) | Read-only Parse.ly or GA4 query |
prc-analytics/analyze-topic | manage_options (via with_site) | Read-only Parse.ly section query |
Source: includes/class-ability.php
prc-analytics/analyze-post
Returns traffic for a post URL from Parse.ly (default) or GA4.
Reference
5 fields
Input
Typed options, defaults, and constraints in one scannable reference.
-
urlurl required -
Post URL to analyze.
-
fromstring -
Period start (provider-specific).
-
tostring -
Period end (provider-specific).
-
sourceenum -
Traffic source.
-
site_idnumber -
Optional multisite blog ID.
No fields match this filter.
Output shape: { source, period, traffic_data }.
Date rules
| Source | Default / max |
|---|---|
| Parse.ly | Most recent 90 days; max span 90 days |
| GA4 | Default trailing 30 days; max span 366 days (historical ranges allowed) |
Common error codes
analytics_invalid_source, parsely_invalid_date, parsely_invalid_date_range, parsely_date_range_too_long, parsely_date_range_too_old, ga_invalid_date, ga_invalid_date_range, ga_date_range_too_long, plus GA provider codes such as ga_invalid_url and ga_service_account.
prc-analytics/analyze-topic
Top-performing posts for a Parse.ly section. Parse.ly only (no GA path).
Reference
5 fields
Input
Typed options, defaults, and constraints in one scannable reference.
-
topicstring required -
Parse.ly section / topic name.
-
fromstring -
Period start.
-
tostring -
Period end.
-
limitnumber -
Result limit (1–100).
-
site_idnumber -
Optional multisite blog ID.
No fields match this filter.