Skip to main content
Glama

Social0

get_analytics

Read-onlyIdempotent

Live performance metrics for posts published through Social0 in a date window: totals, per-platform breakdown, daily series, and top posts. Metrics are read from each network at call time. Use when the user asks how their posts are doing, which platform performs best, or for engagement/views numbers. Example: 'How did my posts do last month?'

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
freshNoBypass warm cache and re-read the platform APIs. Entries younger than 90s are still served from cache.
rangeNoLookback window. Use custom with since/until.7d
sinceNoISO 8601 start (range=custom)
untilNoISO 8601 end (range=custom)
accountNoConnected account UUID or unambiguous platform name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: "Metrics are read from each network at call time," which signals live upstream reads, latency, and potential rate-limit exposure rather than serving snapshots.

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 definition is front-loaded with the core capability and then the when-to-use triggers, with no wasted framing. The closing example quote partially restates the preceding sentence, keeping it just short of fully economical.

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 five-parameter read tool with no output schema, the description compensates well by naming the return shape (totals, per-platform breakdown, daily series, top posts) and the live-read behavior. It stops short of answering practical questions such as how many top posts are returned or what appears when no posts fall in the window.

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%, so range, since/until, fresh, and account are already documented in the schema, and the baseline is 3. The description's only parameter contribution is the phrase "date window," which loosely maps to range but adds no syntax or interaction detail (e.g., that fresh is irrelevant under 90s).

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 a specific resource and verb-equivalent ("Live performance metrics for posts published through Social0 in a date window") and enumerates the four outputs: totals, per-platform breakdown, daily series, and top posts. It does not explicitly distinguish itself from the sibling get_post_analytics, so the agent must infer that this tool is aggregate-level while that one is per-post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete triggers — "how their posts are doing," "which platform performs best," or "engagement/views numbers" — and supplies a realistic example query. It has no exclusionary guidance pointing to get_post_analytics for single-post drill-downs or suggest_best_platforms for planning.

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.