Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Analytics summary

get_analytics_summary
Read-onlyIdempotent

Retrieve views, revenue, and subscriber totals for a chosen lookback period to review blog performance and track growth trends.

Instructions

Get analytics summary (views, revenue, subscribers) for a time period

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to look back (default: 30, max: 365)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv5.1.3
    • changedInput schema / properties / days / description
      Previous value: -"Size of the trailing window in days, ending today. 1-365, defaults to 30. Use 7 for a week, 365 for a year."New value: +"Number of days to look back (default: 30, max: 365)"
  3. Changed1 schema field changedv5.1.0
    • changedInput schema / properties / days / description
      Previous value: -"Number of days to look back (default: 30, max: 365)"New value: +"Size of the trailing window in days, ending today. 1-365, defaults to 30. Use 7 for a week, 365 for a year."
  4. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds the metrics returned and the time-scoping concept, but nothing about aggregation behavior, rate limits, or data freshness beyond what annotations provide.

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, front-loaded sentence with no wasted words. The metric list is the most valuable content and appears early.

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?

For a simple read-only tool with one optional parameter and no output schema, the description is largely sufficient: it names the metrics returned, which substitutes for return-value detail. A note on the default window or aggregation granularity would make it complete.

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 the single 'days' parameter is documented in the schema with default and max constraints. The description's phrase 'for a time period' only loosely echoes the parameter without adding format or boundary details, so baseline 3 applies.

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 uses a specific verb (Get) and resource (analytics summary) and enumerates the metrics returned (views, revenue, subscribers) over a time period. This clearly distinguishes it from sibling tools like get_reputation or status, though it doesn't explicitly name an alternative.

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 implied by 'for a time period,' suggesting it's the tool for aggregate metrics over a window. However, there is no explicit when-to-use guidance, no mention of the default 30-day window, and no stated alternatives or exclusions.

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

Deploy Server

Other Tools