Skip to main content
Glama
Sign In

dopost

by co.dopost.mcp
OverviewDiscussionsAdmin

Get Content Insights

get_content_insights
Read-onlyIdempotent

Read Best Time, Best Day, Format Opportunity, and Platform Pulse with readiness and sample counts. Insufficient samples are returned as readiness state, not a tool error. Requires analytics:read.

Input Schema

NameRequiredDescriptionDefault
daysNoRolling day range. Defaults to 30
endDateNoCustom range end date (ISO 8601); requires startDate
groupIdNo
metricsNo
platformNo
accountIdNo
startDateNoCustom range start date (ISO 8601); requires endDate
accountIdsNo
comparisonNoDefaults to "previous"
workspaceIdNoWorkspace ID from list_workspaces. Required for workspace-wide analytics when the connection has access to multiple workspaces; omit when accountId uniquely identifies the target
includeSeriesNoInclude daily series. Defaults to false and is limited to 90 days

Output Schema

NameRequiredDescriptionDefault
metaYes
insightsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / metrics / items / enum
      Previous value: -[
-  "followers",
-  "followerGrowth",
-  "views",
-  "reach",
-  "engagements",
-  "likes",
-  "comments",
-  "shares",
-  "saves",
-  "impressions",
-  "clicks",
-  "profileViews",
-  "profileVisits",
-  "replies",
-  "reposts",
-  "quotes",
-  "reactions",
-  "pinClicks",
-  "outboundClicks",
-  "pinClickRate",
-  "outboundClickRate",
-  "saveRate",
-  "engagementRate",
-  "videoViews",
-  "engagedViews",
-  "watchTimeMin",
-  "avgViewDuration",
-  "averageViewPercentage",
-  "follows",
-  "unfollows",
-  "subscribersGained",
-  "subscribersLost"
-]New value: +[
+  "followers",
+  "followerGrowth",
+  "views",
+  "reach",
+  "engagements",
+  "likes",
+  "comments",
+  "shares",
+  "saves",
+  "impressions",
+  "clicks",
+  "profileViews",
+  "profileVisits",
+  "replies",
+  "reposts",
+  "quotes",
+  "reactions",
+  "pinClicks",
+  "outboundClicks",
+  "pinClickRate",
+  "outboundClickRate",
+  "saveRate",
+  "engagementRate",
+  "videoViews",
+  "engagedViews",
+  "watchTimeMin",
+  "avgViewDuration",
+  "averageViewPercentage",
+  "follows",
+  "unfollows",
+  "subscribersGained",
+  "subscribersLost",
+  "googleSearchDesktopImpressions",
+  "googleSearchMobileImpressions",
+  "googleMapsDesktopImpressions",
+  "googleMapsMobileImpressions",
+  "websiteClicks",
+  "callClicks",
+  "directionRequests",
+  "messagingClicks",
+  "bookings",
+  "menuClicks"
+]
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "FACEBOOK",
-  "INSTAGRAM",
-  "INSTAGRAM_DIRECT",
-  "THREADS",
-  "PINTEREST",
-  "YOUTUBE",
-  "LINKEDIN",
-  "LINKEDIN_ORGANIZATION",
-  "BLUESKY",
-  "X",
-  "MASTODON"
-]New value: +[
+  "FACEBOOK",
+  "INSTAGRAM",
+  "INSTAGRAM_DIRECT",
+  "THREADS",
+  "PINTEREST",
+  "YOUTUBE",
+  "LINKEDIN",
+  "LINKEDIN_ORGANIZATION",
+  "BLUESKY",
+  "X",
+  "MASTODON",
+  "GOOGLE_BUSINESS"
+]
    • changedOutput schema / properties / meta / properties / filters / properties / metrics / items / enum
      Previous value: -[
-  "followers",
-  "followerGrowth",
-  "views",
-  "reach",
-  "engagements",
-  "likes",
-  "comments",
-  "shares",
-  "saves",
-  "impressions",
-  "clicks",
-  "profileViews",
-  "profileVisits",
-  "replies",
-  "reposts",
-  "quotes",
-  "reactions",
-  "pinClicks",
-  "outboundClicks",
-  "pinClickRate",
-  "outboundClickRate",
-  "saveRate",
-  "engagementRate",
-  "videoViews",
-  "engagedViews",
-  "watchTimeMin",
-  "avgViewDuration",
-  "averageViewPercentage",
-  "follows",
-  "unfollows",
-  "subscribersGained",
-  "subscribersLost"
-]New value: +[
+  "followers",
+  "followerGrowth",
+  "views",
+  "reach",
+  "engagements",
+  "likes",
+  "comments",
+  "shares",
+  "saves",
+  "impressions",
+  "clicks",
+  "profileViews",
+  "profileVisits",
+  "replies",
+  "reposts",
+  "quotes",
+  "reactions",
+  "pinClicks",
+  "outboundClicks",
+  "pinClickRate",
+  "outboundClickRate",
+  "saveRate",
+  "engagementRate",
+  "videoViews",
+  "engagedViews",
+  "watchTimeMin",
+  "avgViewDuration",
+  "averageViewPercentage",
+  "follows",
+  "unfollows",
+  "subscribersGained",
+  "subscribersLost",
+  "googleSearchDesktopImpressions",
+  "googleSearchMobileImpressions",
+  "googleMapsDesktopImpressions",
+  "googleMapsMobileImpressions",
+  "websiteClicks",
+  "callClicks",
+  "directionRequests",
+  "messagingClicks",
+  "bookings",
+  "menuClicks"
+]
  2. First observed

TDQS

B3.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish the safe read-only, idempotent profile, so the bar is lower. The description adds genuinely useful context beyond them: the auth scope required and, importantly, that insufficient samples return a readiness state instead of an error, which prevents an agent from misinterpreting a sparse result as a failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the payload description front-loaded, followed by the edge-case behavior and the auth requirement. No filler, though the insight names could be more self-explanatory for an unfamiliar agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, and the readiness-state note covers the main failure mode. However, for an 11-parameter analytics tool with only 55% schema coverage and no sibling routing, the description leaves real gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 55% across 11 parameters, and the description explains none of them. Several params (metrics, platform, accountId, accountIds, groupId) lack schema descriptions, and the description does nothing to compensate for those gaps or clarify the days vs startDate/endDate vs includeSeries interaction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Read') and enumerates the concrete artifacts returned (Best Time, Best Day, Format Opportunity, Platform Pulse), which separates it from get_analytics_overview and get_audience_analytics. The named insights are somewhat product-jargon, so the boundaries with siblings are implied rather than stated explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is a precondition ('Requires analytics:read') and a note that insufficient samples surface as readiness state. There is no indication of when to choose this over get_analytics_overview, get_audience_analytics, or get_post_performance, so the agent gets no routing help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dopost toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources