Skip to main content
Glama

Chirpie

by io.github.Firefloco
OverviewDiscussionsAdmin

List comments on a post

chirpie_list_comments
Read-onlyIdempotent

List the comments on a post you published, newest first. Answers from Chirpie's stored snapshot, which is refreshed on a schedule, so the response carries a sync object saying how fresh it is (anything but status ok has a ready-worded sentence in sync.reason) and a capabilities object saying what this platform allows: reply, hide, delete_own and delete_any. delete_any says whether somebody else's comment can be deleted. Page with next_cursor. Listing costs nothing, but replying publishes a post and so uses one post from the monthly quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
syncNo'auto' (default) refreshes when the platform's refresh window has passed, 'true' asks for a refresh now (honoured a minute after the last refresh, 15 minutes on X; sync.next_sync_after says when), 'false' reads what is stored without one
limitNoComments to return (default 25, max 100)
sinceNoISO 8601 datetime: only comments posted after it
cursorNoThe next_cursor from the previous page
post_idYesPost ID whose comments to list
include_hiddenNoInclude comments you have hidden (they carry hidden: true)
include_deletedNoInclude deleted comments (they carry deleted: true and keep the last text Chirpie stored). Deleting a comment on Facebook, Instagram, Threads or LinkedIn deletes its replies too

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include_deleted / description
      Previous value: -"Include deleted comments (they carry deleted: true and keep the last text Chirpie stored). Deleting a comment on LinkedIn, or on Facebook, Instagram or Threads (coming soon), deletes its replies too"New value: +"Include deleted comments (they carry deleted: true and keep the last text Chirpie stored). Deleting a comment on Facebook, Instagram, Threads or LinkedIn deletes its replies too"
  2. Changed1 schema field changed
    • changedInput schema / properties / include_deleted / description
      Previous value: -"Include deleted comments (they carry deleted: true and keep the last text Chirpie stored). Deleting a comment on Facebook, Instagram, Threads or LinkedIn deletes its replies too"New value: +"Include deleted comments (they carry deleted: true and keep the last text Chirpie stored). Deleting a comment on LinkedIn, or on Facebook, Instagram or Threads (coming soon), deletes its replies too"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, and the description adds substantial context beyond them: snapshot freshness semantics via `sync` and `sync.reason`, per-platform capability flags including `delete_any`, cursor pagination, and the quota cost of the related reply action. This is rich behavioral disclosure.

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?

Purpose is front-loaded in the first sentence and the rest is dense, useful signal. The later sentences are run-on with stacked parentheticals, which slightly hurts scannability but no sentence is wasted.

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 carries the burden of describing the return shape — `sync`, `sync.reason`, `capabilities`, and `next_cursor` — and it does so. An agent has everything needed to call and interpret the result correctly.

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 description coverage is 100%, so every parameter is already documented in the schema (including the `sync` enum values and their refresh windows). The description's 'Page with `next_cursor`' mostly restates schema content, so the baseline 3 applies.

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?

States a specific verb and resource ('List the comments on a post you published') plus the ordering ('newest first'). The scope constraint 'you published' and the capability enumeration implicitly separate it from the mutation siblings (chirpie_reply_to_comment, chirpie_hide_comment, chirpie_delete_comment).

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 clear context for use — read a post's comments from the stored snapshot — and contrasts the free listing with quota-consuming replying, steering the agent away from mutation tools. It stops short of explicitly naming alternative tools or stating when not to use this one.

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

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