Skip to main content
Glama

List Post Performance

list_post_performance
Read-onlyIdempotent

List analytics for posts published through dopost, sorted by a supported performance metric. Returns posts with available analytics. Requires analytics:read.

Input Schema

NameRequiredDescriptionDefault
daysNoRolling day range. Defaults to 30
limitNoResults per call. Defaults to 20
cursorNo
sortByNo
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
postsYes
hasMoreYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
      +]
    • changedOutput schema / properties / posts / items / properties / metrics / items / properties / key / 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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the auth scope ('Requires analytics:read') and a return-behavior note ('Returns posts with available analytics'), which is real value beyond structured fields, though pagination and partial-result semantics are left implicit.

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, front-loaded with the core action and scope, with no filler. Efficient, though the ordering buries the auth requirement after the return note rather than grouping prerequisites.

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 described, and annotations cover safety. However, for a 14-parameter analytics tool with multiple overlapping filter groups, the description does not explain how the filters interact or when the workspace/account identifiers matter, leaving the agent to reconstruct behavior from the schema alone.

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 coverage is only 50% across 14 parameters, and the description compensates for almost none of the gap: it gestures at sortBy ('sorted by a supported performance metric') but says nothing about days vs. startDate/endDate, cursor, accountId vs. accountIds, groupId, comparison, or includeSeries. The undocumented half of the surface stays undocumented.

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 and resource ('List analytics for posts published through dopost') plus a qualifying behavior (sorted by a supported performance metric). It is clear what the tool does, but it never distinguishes itself from the closely-named sibling get_post_performance or from get_analytics_overview, so the agent must infer that this is the bulk/list variant.

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

Usage Guidelines3/5

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

The description supplies a prerequisite ('Requires analytics:read') but gives no when-to-use guidance against get_post_performance, get_analytics_overview, or get_content_insights. Usage is only implied by the plural 'List' framing and the sort/filter surface.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources