Skip to main content
Glama
Sign In

Acrium

by com.acriumautomated
OverviewDiscussionsAdmin

List post comments

list_post_comments
Read-onlyIdempotent

The comments on one published post, newest first: each with its comment_id, platform, author's handle, text, time, and replied (whether a reply to it already went out through Acrium). Works on Facebook, Instagram, LinkedIn, Threads, X and Bluesky for posts sent through Outstand. YouTube comment replies are coming soon (read them in YouTube Studio for now); TikTok and Pinterest don't allow it, so those comments are read in the app. New comments also arrive in get_attention_items. Comments on paid or boosted copies (ads) of a post aren't included: read those in Meta Ads Manager or the app.

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": {
      "post_id": "<post_id>"
    },
    "name": "list_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post's id (from publish_post, get_post_stats, or a comment's attention item).
platformNoOnly this platform's comments. Leave out for every platform the post is live on.
project_idNoWorkspace to work in (from list_projects). Leave out for the default one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial extra behavior: newest-first ordering, the exact fields per comment (including 'replied' cross-referencing an Acrium reply), supported platforms, and two explicit scope exclusions (paid/boosted copies, unsupported platforms).

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?

A single dense paragraph that front-loads the core behavior and return shape before moving into platform caveats. Every sentence carries information, though the platform limitation clauses are wordy and could be tightened.

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?

With no output schema, the description compensates by listing returned fields and their meaning, and it covers coverage gaps (ads, YouTube, TikTok/Pinterest) plus a data-freshness pointer to get_attention_items. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so post_id, platform, and project_id are already documented. The description reinforces that the tool is scoped to 'one published post' and clarifies per-platform availability (which gives the platform filter meaning), but adds no syntax or format detail beyond 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?

The description opens with a specific verb and resource ('The comments on one published post, newest first') and enumerates the returned fields, so an agent can distinguish it from get_post_stats or get_attention_items without opening the schema.

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?

It names concrete alternatives and conditions: YouTube replies 'coming soon' so read in YouTube Studio, TikTok/Pinterest not supported so read in the app, ad-copy comments in Meta Ads Manager, and 'New comments also arrive in get_attention_items.' It stops short of stating explicitly when to prefer this tool over get_attention_items, but the surrounding context is strong.

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

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