Skip to main content
Glama

Social0

get_post_analytics

Read-onlyIdempotent

Live metrics for one Social0 post, broken out per network it was published to. Use after list_posts or get_post when the user asks how a specific post performed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post_id": "<post_id>"
    },
    "name": "get_post_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesSocial0 post ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the meaningful detail that results are "live" and organized per network, but says nothing about metric freshness, availability for unpublished posts, or what happens for a post with no data.

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

Conciseness5/5

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

Two sentences with no filler: the capability and output shape come first, then the usage trigger. Nothing is repeated from the schema or annotations.

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 single-parameter read tool with no output schema, the description gives enough to call it correctly and hints at the return shape (per-network metric breakdown). A short note on metric recency or empty-data behavior would close the remaining gap.

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?

There is only one parameter and the schema already documents it fully (uuid, "Social0 post ID"), so the description adds no syntax beyond what the schema supplies. The phrase "one Social0 post" only loosely reinforces that post_id refers to a single post rather than an ID list.

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?

"Live metrics for one Social0 post, broken out per network" gives a specific resource (per-post analytics) and a scope (single post, per-network breakdown) that is scoped more narrowly than a generic analytics tool. It does not explicitly name the sibling it differs from (get_analytics), so an agent must infer that distinction.

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 states a clear trigger ("when the user asks how a specific post performed") and a prerequisite chain ("Use after list_posts or get_post"), which tells the agent both the condition and the ordering. It stops short of stating when NOT to use it, e.g., for account-level or aggregate reporting.

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.