Skip to main content
Glama

DemandBird

by com.demandbird.app
OverviewDiscussionsAdmin

list_top_posts

Read-only

Rank recent posts to answer "what's my best post?", "what was Alex's best post?", "what was our top post this month?", "worst post?". WHOSE POSTS: this workspace may have several people posting, so pass author whenever the question names one. "my"/"mine"/"I" -> author: "me". A person's name -> that name, e.g. author: "Alex". "our"/"the team"/"we", or no one named at all -> omit author for the whole workspace. Do not assume "my" means the workspace. Omit platform to rank across every connected network; pass one to focus. Defaults to ranking by engagement rate. Use order: bottom for worst-performers. Returns each post's id, stats, snippet, and link. Read-only.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many posts (default 5, max 20).
orderNotop (best) or bottom (worst). Default top.
authorNoWhose posts to rank. "me" for the person asking (use this for "my best post"), or a teammate's name for theirs ("Alex"). Omit for the whole workspace, which is the default and is what "our" / "the team" means.
metricNoWhat to rank by. Default engagement_rate. discussion_rate is comments per 1,000 impressions. LinkedIn also tracks profile_views (profile viewers the post drove), members_reached, saves, sends, follows, lift, clicks and premium_cta_clicks (clicks on a Premium member's profile button that came from the post); other platforms track their own subset. A metric a platform doesn't report is refused with the list it does.
periodNoRolling window ending today. Default 30d. For any other window, pass start_date/end_date instead.
end_dateNoOptional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date.
platformNoOptional. Omit to rank across all platforms.
start_dateNoOptional. First day of a custom range, YYYY-MM-DD, in the user's timezone. Use for windows the presets don't cover: "last 14 days", "in March", "since Jan 1", "last year". Overrides `period`. Ranges can cover up to 366 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only/non-destructive profile, yet the description still adds the default ranking metric, cross-platform default scope, and the returned fields (id, stats, snippet, link). It repeats "Read-only" from annotations but contributes genuine behavioral defaults beyond them.

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 question examples, then labeled sections ("WHOSE POSTS") make it scannable. The author-routing block is somewhat verbose for what it says, but each sentence resolves a real ambiguity.

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?

Eight all-optional parameters and no output schema, so the description carries the burden of stating defaults, return shape, and the "me" vs name vs workspace ambiguity — all of which it does. Nothing an agent needs to call this correctly 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 goes further by mapping natural-language cues onto `author` and explaining the platform-omission semantics in prose. The remaining parameters (period vs start/end, limit) are left entirely to the schema.

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?

Opens with a specific verb+resource ("Rank recent posts") and anchors it with four concrete user questions, which immediately separates ranking from the many `list_*` siblings. An agent can tell this is a ranked-best/worst query, not a chronological listing.

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?

Explicitly routes the ambiguous cases: "my"/"mine" -> author: "me", a name -> that name, "our"/"team"/no one -> omit author, with an explicit warning not to assume "my" means workspace. Also states order: bottom for worst-performers and when to omit vs pass platform.

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

All DemandBird 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