PostRite

Get top posts by engagement

get_top_posts

Read-only

Rank the organization's posts by an engagement metric over a period. Defaults to overall engagement (sum of all metrics). Returns at most the 10 best posts: there is no limit or page parameter, so narrow days or change metric to see others. Each post may carry media — a reference to its first media item in the library ({id, mimeType, hasThumbnail}), not a URL; null when the post has no media.

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

Name	Required	Description
`days`	No	Period in days (7, 30, 90; default 30)
`metric`	No	Metric to rank by (default: engagement)
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description
`days`	No
`posts`	No
`metric`	No	The metric the ranking used

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare the read-only, non-destructive, open-world profile; the description adds genuinely new behavior: the default ranking metric, a hard 10-result cap with no pagination escape hatch, and the shape/semantics of the returned `media` field (a library reference, not a URL, null when absent). These are exactly the non-obvious traits an agent needs before calling and interpreting results.

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?

Three tight sentences, front-loaded with the core operation, then the truncation caveat, then the payload caveat. Every sentence carries information an agent would otherwise have to discover by trial.

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

Completeness5/5

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

All three parameters are fully documented in the schema, annotations cover the safety profile, and an output schema exists so return structure need not be spelled out. The description still covers the two things the schema cannot: the result cap and the `media` reference semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by tying `days` and `metric` to the 10-item cap — narrowing the window or switching metric is how you surface posts that would otherwise be truncated. That is real semantic linkage rather than restating the enum values.

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

Purpose5/5

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

The first sentence states a specific verb and resource with scope: "Rank the organization's posts by an engagement metric over a period." It also signals what the tool is not by noting there is no limit or page parameter, which implicitly contrasts it with the paginated listing siblings like list_posts.

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?

Gives explicit operational guidance: the default metric is overall engagement, results are capped at 10, and the way to see more is to narrow `days` or change `metric`. It does not name alternative siblings (e.g. get_post_analytics, list_posts) or state when to prefer them, so no true alternatives/exclusions guidance.

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

All PostRite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?