Skip to main content
Glama

Post engagement curve

get_post_performance
Read-onlyIdempotent

Every metric capture for one published post (1h/24h/72h/7d/30d), attributed to its plan and content item. Platforms without a measurable API return status 'unsupported' rather than a zero.

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": {
      "queue_id": "<queue_id>"
    },
    "name": "get_post_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
queue_idYesThe publish queue row id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real behavioral context beyond that: the fixed capture cadence, that metrics are attributed to a plan and content item, and that non-measurable platforms return 'unsupported' instead of zero — a distinction that prevents misreading a null result as no engagement.

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, both load-bearing: the first defines the payload and its time buckets, the second pre-empts the most likely misreading of the result. No filler, no restatement of the tool name.

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 one-parameter read tool with no output schema, the description does the needed work: it sketches the return shape (metric captures across five windows, with plan/content attribution) and flags the 'unsupported' sentinel. Only the provenance of queue_id, presumably from list_publish_queue, is left unstated.

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?

With a single parameter and 100% schema description coverage, the schema already tells the agent that queue_id is the publish queue row id. The description adds nothing about that identifier — notably it never explains how a post maps to a queue row, which is the one semantic gap the schema leaves.

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 (metric captures for one published post) and enumerates the measurement windows (1h/24h/72h/7d/30d), which is far more informative than the title alone. It implies per-post scope, distinguishing it in spirit from aggregate tools like get_performance_digest, but it never names a sibling, so the differentiation is left to inference.

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: 'one published post' suggests a single-post drilldown rather than a portfolio view, but there is no explicit 'use this when…' clause and no pointer to get_performance_digest or get_top_posts for aggregate cases. An agent can guess the right context, but must guess.

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