Skip to main content
Glama

get_post_analytics

Retrieve analytics metrics for published social media posts, including impressions, reactions, engagements, clicks, shares, comments, and video views over specified time periods.

Instructions

Get analytics metrics for individual published posts.

Post-level metrics use the 'lifetime.' prefix (e.g. 'lifetime.impressions').
Common metrics: lifetime.impressions, lifetime.reactions, lifetime.engagements,
                lifetime.clicks, lifetime.shares, lifetime.comments, lifetime.video_views.

Args:
    profile_ids: Comma-separated Sprout profile IDs.
    start_time: Start of period (ISO 8601, e.g. '2024-01-01T00:00:00').
    end_time: End of period (ISO 8601, e.g. '2024-01-31T23:59:59').
    metrics: Comma-separated metric names with lifetime. prefix.
    limit: Number of posts to return (default 50, max 100).
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_idsYes
start_timeYes
end_timeYes
metricsNolifetime.impressions,lifetime.reactions,lifetime.engagements,lifetime.clicks
limitNo
customer_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's function and parameter usage, but lacks details on permissions, rate limits, error conditions, or pagination behavior. The mention of default values and environment variable fallback adds some context.

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?

The description is well-structured with a clear purpose statement, metric examples, and a parameter breakdown. It is appropriately sized but could be slightly more concise by integrating the metric examples into the parameter description for metrics.

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

Completeness4/5

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

Given the tool's complexity (6 parameters, no annotations) and the presence of an output schema, the description is largely complete. It covers parameter semantics thoroughly and provides usage context, though additional behavioral details (e.g., error handling) would enhance completeness.

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

Parameters5/5

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

The description provides comprehensive parameter semantics beyond the input schema, which has 0% description coverage. It explains the purpose of each parameter (e.g., 'Comma-separated Sprout profile IDs'), format requirements (ISO 8601), naming conventions ('lifetime.' prefix), default values, and environment variable fallback for customer_id.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Get analytics metrics for individual published posts.' It specifies the verb ('Get'), resource ('analytics metrics'), and scope ('individual published posts'), distinguishing it from sibling tools like get_profile_analytics (which likely focuses on profile-level metrics).

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 implies usage context by specifying 'individual published posts' and listing common metrics, but does not explicitly state when to use this tool versus alternatives like get_profile_analytics or other sibling tools. No guidance on prerequisites or exclusions is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jmeserve/sprout-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server