Skip to main content
Glama
Sign In

oriiion

by ai.oriiion
OverviewDiscussionsAdmin

Get Top Performing Posts

get_top_posts
Read-onlyIdempotent

The account's published posts as they are on the platforms, including posts made outside oriiion, with captions, platforms, media type and metrics. By default the best performers by engagement: study these to learn what content resonates and create more of what works. With sort 'recent' the newest first: use that for 'what's our latest post' or 'can you see my videos/feed'. mediaType 'video' is a video post (on Instagram a Reel or a feed video); a 'carousel' can hold videos too.

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
daysNoLook-back window in days. Default 30, or 365 with sort 'recent' — omit it when asking for the latest posts
sortNo'engagement' for the best performers, 'recent' for the newest posts firstengagement
limitNoHow many posts to return
platformNoFilter to one platformall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / days / default
      Removed value: -30
    • changedInput schema / properties / days / description
      Previous value: -"Look-back window in days"New value: +"Look-back window in days. Default 30, or 365 with sort 'recent' — omit it when asking for the latest posts"
    • changedInput schema / properties / limit / description
      Previous value: -"How many top posts to return"New value: +"How many posts to return"
    • addedInput schema / properties / sort
      Added value: +{
+  "default": "engagement",
+  "description": "'engagement' for the best performers, 'recent' for the newest posts first",
+  "enum": [
+    "engagement",
+    "recent"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real behavioral context on top: the data set includes posts published outside the product, and the response carries captions, platform, media type and metrics. It does not mention result caps or what happens when there are no posts, which keeps it below a 5.

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?

Front-loaded with the resource and return content, then default behavior, then the recent-mode alternative — good ordering with no filler. It is dense to the point of being slightly run-on in the media-type sentence, but every clause carries information.

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?

With four optional params, no output schema and rich annotations, the description covers defaults, alternative modes and media-type edge cases adequately. Minor gaps remain (no sense of result volume behavior or empty-set handling), but nothing essential for correct invocation is missing.

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 the baseline is 3, but the description adds interpretation the schema lacks: what 'recent' means in practice, and that mediaType 'video' includes Instagram Reels and feed videos while a 'carousel' can hold videos. That directly prevents a common filtering mistake.

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 states a specific resource and scope: the account's published posts as they exist on the platforms, including posts made outside oriiion, with captions, platforms, media type and metrics. The default behavior (best performers by engagement) separates it from a plain list_posts, but the description never names the nearby siblings (list_posts, get_post, get_top_performing_media), so the distinction has to be inferred.

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

Usage Guidelines5/5

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

It explicitly gives when-to-use for each mode: the default engagement sort is for studying what content resonates, and sort 'recent' is for 'what's our latest post' or 'can you see my videos/feed'. Concrete user-phrasing triggers are supplied, leaving little to inference.

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

All oriiion toolsInspect
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