Skip to main content
Glama

Zernio

by com.zernio
OverviewDiscussionsAdmin

Get post analytics

analytics_get_analytics
Read-only

Get post analytics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoPage size (default 50)
orderNoSort orderdesc
sourceNoFilter by post source: late (posted via Zernio API), external (synced from platform), all (default)all
post_idNoReturns analytics for a single post. Accepts both Zernio Post IDs and External Post IDs. Zernio IDs are auto-resolved to External Post analytics.
sort_byNoSort by date, engagement, or a specific metric. Platform-specific metrics (follows, reposts, reels_skip_rate, ig_reels_*, completion_rate, profile_views) sort a null value as 0.date
to_dateNoInclusive upper bound (YYYY-MM-DD). Defaults to today if omitted.
platformNoFilter by platform (default "all")
from_dateNoInclusive lower bound (YYYY-MM-DD). Defaults to 90 days ago if omitted. Max range is 366 days.
account_idNoFilter by account ID
profile_idNoFilter by profile ID (default "all")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort by date, engagement, or a specific metric. Instagram-only metrics (follows, reposts, reels_skip_rate, ig_reels_*) sort a null value as 0."New value: +"Sort by date, engagement, or a specific metric. Platform-specific metrics (follows, reposts, reels_skip_rate, ig_reels_*, completion_rate, profile_views) sort a null value as 0."
  2. Changed1 schema field changed
    • changedInput schema / properties / account_id / description
      Previous value: -"Filter by social account ID"New value: +"Filter by account ID"
  3. Changed1 schema field changed
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort by date, engagement, or a specific metric. Instagram-only metrics (follows, reposts, reels_skip_rate, ig_reels_*) sort posts with no value as 0."New value: +"Sort by date, engagement, or a specific metric. Instagram-only metrics (follows, reposts, reels_skip_rate, ig_reels_*) sort a null value as 0."
  4. Changed1 schema field changed
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort by date, engagement, or a specific metric"New value: +"Sort by date, engagement, or a specific metric. Instagram-only metrics (follows, reposts, reels_skip_rate, ig_reels_*) sort posts with no value as 0."
  5. First observed

TDQS

C2.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds no behavioral context beyond those structured hints. It does not contradict the annotations, but it also provides no additional information about pagination implications, data scope, or any side effects.

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

Conciseness2/5

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

The description is technically short but is under-specified: three words that restate the title and provide no useful structural information. This is not effective conciseness but a failure to provide any added value.

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?

The rich input schema and annotations cover a lot of operational details, and the existence of an output schema helps, so the definition is minimally viable for invoking the tool. However, the description itself is too thin to clarify the analytical scope relative to four sibling analytics tools, and leaves the agent to infer the endpoint's true semantics from parameter names.

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

Parameters3/5

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

Schema description coverage is 100%, and each parameter has meaningful descriptions with defaults, formats, and filter semantics (e.g., date bounds, source, post_id resolution). The tool description itself adds no parameter-level meaning, so the baseline of 3 is appropriate since the schema carries the full semantic load.

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

Purpose2/5

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

Tautological: description restates name/title.

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?

No guidance is given about when to call this tool versus the other analytics tools. There are no mention of alternatives, exclusions, or conditions that would help an agent choose analytics_get_analytics over analytics_get_daily_metrics or analytics_get_post_timeline.

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

All Zernio 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