Skip to main content
Glama

Top published posts

get_top_posts
Read-onlyIdempotent

Published posts with their reach and engagement metrics.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/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 that results are limited to published posts and include reach and engagement metrics, which is useful behavioral context, but it says nothing about ordering (e.g. top by what metric), pagination, or how account scoping affects results.

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

Conciseness3/5

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

The single fragment is compact with no wasted words, but it is a noun phrase rather than a complete, front-loaded statement of action and scope. Brevity here reflects under-specification rather than efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 0% schema description coverage, the description carries most of the explanatory burden and falls short. It omits what "top" means (ranking criterion), result ordering, default and maximum result counts, and the role of account_id.

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% for both parameters, so the description must compensate and it does not: neither limit (default 20, max 100) nor account_id is mentioned. An agent learns nothing from the description about whether results are scoped to one account or how many are returned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Published posts with their reach and engagement metrics" identifies the resource and hints at returned fields, but there is no verb (e.g. "list") and no differentiation from the similar sibling get_post_performance. An agent can guess it retrieves published posts, but cannot confidently separate it from performance-related siblings.

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 when-to-use guidance, no mention of alternatives such as get_post_performance or get_content_assets, and no stated preconditions. The only implicit cue is the word "Published," which suggests it excludes drafts and scheduled items, but this is never stated.

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