Skip to main content
Glama

Get publishing analytics

mynahcast_get_analytics
Read-onlyIdempotent

Published and failed posts per day, per channel and by hour of day, over the plan's analytics history. days defaults to 30; the plan caps it (Creator 30, Pro 90, Team 365, Agency 730) and the answer says when it was clamped. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mynahcast_get_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
brandIdNo

Output Schema

NameRequiredDescriptionDefault
toYes
daysYes
fromYes
byDayYes
byHourYes
totalsYes
clampedYes
byChannelYes
retentionDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / byChannel / items / properties / provider / enum
      Previous value: -[
      -  "bluesky",
      -  "mastodon",
      -  "telegram",
      -  "discord",
      -  "x",
      -  "linkedin",
      -  "youtube",
      -  "tumblr",
      -  "nostr",
      -  "lemmy",
      -  "misskey",
      -  "slack",
      -  "matrix",
      -  "devto",
      -  "hashnode",
      -  "wordpress",
      -  "listmonk"
      -]New value: +[
      +  "bluesky",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "x",
      +  "linkedin",
      +  "youtube",
      +  "tumblr",
      +  "nostr",
      +  "lemmy",
      +  "misskey",
      +  "slack",
      +  "matrix",
      +  "devto",
      +  "hashnode",
      +  "wordpress",
      +  "listmonk",
      +  "instagram",
      +  "threads",
      +  "facebook"
      +]
  2. First observed

TDQS

A3.7/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 'Read-only' in the description is redundant with structured data. However, the description adds genuine behavioral context beyond the annotations: per-plan retention caps (Creator 30, Pro 90, Team 365, Agency 730) and the fact that the response discloses when the range was clamped — information an agent cannot get from the schema or annotations. It does not describe response shape or cost/latency, which keeps it below 5.

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 compact sentences with no filler, and the most useful information (what the output contains, then the days cap behavior) is front-loaded. The trailing 'Read-only' is a wasted clause given the annotations, but overall structure is tight.

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?

An output schema exists, so the description need not explain return values, and the retention-cap/clamping disclosure covers the main behavioral risk for a 2-parameter analytics read. The only material gap is the unexplained `brandId` scope (whether it filters the aggregate or selects an account context), which an agent would have to infer.

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 0%, so the description carries the burden for both parameters. It handles `days` well — default 30, tier-based maximum, and the clamping notice — adding meaning the bare integer constraint does not convey. The `brandId` parameter is never mentioned in the description and has no schema description, leaving one of two parameters semantically 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?

The description states a concrete resource set (published and failed posts) with three explicit breakdown dimensions (per day, per channel, by hour of day) and scopes it to the plan's analytics history. An agent can tell this is an aggregate analytics tool rather than a post-listing tool. It does not name a sibling (e.g., get_report) to sharpen the boundary, which keeps it from a 5.

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?

Usage is only implied by the resource it returns; there is no explicit 'use this when you need X instead of get_report/get_post_timeline' guidance or any stated prerequisite. An agent can infer the analytics use case but must guess the boundary against the other reporting siblings.

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