Skip to main content
Glama

SocialToAI

by com.socialtoai
OverviewDiscussionsAdmin

Read comments

comments
Read-only

Read the comments under one piece of content. Read-only. Each line: what to pass (a|b: either one), then platforms at 2 credits a call unless numbered. A list of platforms, ids or links: a call each. Failed calls cost 0. Need 100 items? Pass limit=100 (a call a page). Give id: bilibili, facebook, wechat_channels 12, x, zhihu Give id|url: douyin, instagram, kuaishou, reddit, tiktok, weibo, xiaohongshu 12, youtube Give url: wechat 12 With reply_of: bilibili, douyin, instagram, kuaishou, tiktok, wechat 12, wechat_channels 9, xiaohongshu 12, youtube, zhihu More parameters: capabilities. Pass links whole, as given. On error, follow error.fix. Tell the user billing.display.

Input Schema

NameRequiredDescriptionDefault
idNo
urlNo
sortNoBy platform: best, latest, popular
limitNoHow many items you want: pages are fetched one after another in this one call until there are that many or no more, each page charged as a call; pages not needed cost 0. Need 100 items? Pass limit=100.
cursorNopage.cursor of the last answer, other arguments unchanged.
handleNoA handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run.
platformYesOne, or a list.
reply_ofNo
max_cost_creditsNoRefused, free, if the call would cost more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / handle / description
      Previous value: -"A handle an earlier answer gave: reads that result, free. Nothing else is run."New value: +"A handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run."
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many items you want: pages are fetched one after another in this one call until there are that many or no more, each page charged as a call; pages not needed cost 0. Need 100 items? Pass limit=100.",
+  "type": "integer"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations: per-call credit costs, zero cost for failed calls, pagination charging, error recovery via error.fix, and billing.display notification.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the subsequent platform rules use cryptic notation (e.g., 'a|b: either one', numbers without units) that hinders parsing. It is compact but not optimally structured for quick comprehension.

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 tool with no output schema and 67% schema coverage, the description adequately covers platform-specific invocation, pagination via limit, error recovery, and cost. It gives enough context to call the tool correctly, though the cryptic notation leaves some room for misinterpretation.

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?

With 67% schema description coverage, the schema covers some parameters but not platform-specific requirements. The description adds significant meaning by mapping which platforms require id, id|url, or url, and which support reply_of, plus credit cost hints—information not present in the schema.

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 verb and resource: 'Read the comments under one piece of content. Read-only.' It is clear what the tool does, but it does not differentiate itself from the sibling tool comment_insights, leaving ambiguity about when to choose one over the other.

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

Usage Guidelines3/5

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

The description provides detailed invocation guidance—which platforms accept id, url, or reply_of, and how to use limit for pagination. However, it offers no explicit guidance on when to use this tool versus alternatives like comment_insights or search, so usage is only implied by the purpose.

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

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