Skip to main content
Glama

Post analytics overview

get_analytics
Read-onlyIdempotent

Your published posts with views, likes and comments per network, totals, the best time to post and views per day.

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": "get_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
rangeNo
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful fact that no output schema exists, by enumerating returned data categories (totals, best time to post, views per day), but it says nothing about default range, aggregation semantics, or whether results span all profiles when profile_id is omitted.

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?

A single compact sentence with no filler, and the most important content (what data you get) is front-loaded. It loses a point for being a fragment that reads as a return-value list rather than an actionable definition.

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?

With no output schema and no annotations describing results, the description is the only source of return-value information, and it does list the data categories. However, for a three-parameter analytics tool it leaves open the default time range, per-profile scoping, and sorting behavior, which an agent needs to call it correctly.

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 0%, so the description carries the burden for all three parameters, yet it never mentions sort, range, or profile_id. Only the enums in the schema give any hint of what valid values mean, and there is no indication of defaults or how profile_id scopes the result.

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 names the resource concretely: published posts with views, likes, comments per network, totals, best time to post, and views per day. It is clear what data the agent gets back, but it is a noun-phrase fragment with no verb and it makes no attempt to distinguish itself from the sibling get_post_analytics.

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?

There is no statement of when to call this tool, when not to, or which sibling to prefer for per-post versus overview analytics. The agent must infer the overview-vs-single-post split purely from tool names.

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.