Skip to main content
Glama

Social0

list_inbox_comments

Read-onlyIdempotent

Read comment threads on posts published through Social0, fetched live from each network. Each thread carries the comment_id and publication_id needed to reply, like, or hide. Use when the user asks what people are saying, or wants to triage replies. Example: 'Any comments I haven't answered?'

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": "list_inbox_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass warm cache and re-read the platform APIs. Entries younger than 90s are still served from cache.
limitNo
rangeNoLookback window. Use custom with since/until.7d
sinceNoISO 8601 start (range=custom)
untilNoISO 8601 end (range=custom)
beforeNoCursor from a previous response's next_before
accountNoConnected account UUID or unambiguous platform name
platformNoLimit to one platform (e.g. bluesky, twitter_x, youtube)
unanswered_onlyNoOnly threads the connected account has not replied to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds useful chaining context — each thread carries comment_id and publication_id for reply/like/hide — but says nothing about result volume, pagination behavior, or rate limits beyond what the schema states.

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?

Three tight sentences, front-loaded with the core action and followed by usage context and an example. The example is short and reinforces the triage use case rather than padding.

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?

For a 9-parameter read tool with no output schema, the description usefully discloses the shape of returned threads (comment_id, publication_id), compensating for the missing output schema. Remaining gaps around pagination and result limits are modest given the rich schema descriptions and annotations.

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 89%, so parameters like fresh, range, before and unanswered_only are already well documented in the schema. The description adds no parameter-level meaning beyond that baseline, dedicating its content to purpose and returned fields instead.

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?

States a specific verb and resource ('Read comment threads on posts published through Social0') and clarifies the data source ('fetched live from each network'). It implicitly distinguishes itself from list_inbox_dms by scoping to comments on published posts, though it never names the sibling explicitly.

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 when-to-use guidance ('what people are saying', 'triage replies') plus a concrete example trigger. It lacks any when-not-to-use or named alternative for cases like DMs or single-thread retrieval.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.