Skip to main content
Glama

SocialToAI

by com.socialtoai
OverviewDiscussionsAdmin

Read trending lists

trending
Read-only

Read a platform's trending list. Read-only. Each line: what to pass, then platforms at 2 credits a call unless numbered. A list of platforms: a call each. Failed calls cost 0. Need 100 items? Pass limit=100 (a call a page). Needs no parameter: bilibili, douyin, kuaishou, reddit, weibo, x 6, xiaohongshu 12, zhihu With type=videos: bilibili, douyin With type=trends: reddit More parameters: capabilities. On error, follow error.fix. Tell the user billing.display.

Input Schema

NameRequiredDescriptionDefault
typeNoBy platform: videos, trends
boardNoBy platform: hot_search, rising, topics, searches, music, low_fan, high_like, high_completion, high_follow, popular, trends, inspiration, hot
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.
regionNoWhich country's trends, by its two-letter code: US, GB, CA, AU, IN, JP, DE, FR, BR or MX; worldwide when left out
platformYesOne, or a list.
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.8/5.0
Behavior5/5

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

Annotations already establish read-only, open-world, non-destructive behavior, but the description adds substantial operational context: 2 credits per call unless numbered, one call per listed platform, failed calls cost 0, pagination is charged per page, max_cost_credits refusals are free, and handle rereads are free. It also tells the agent to follow error.fix and tell the user billing.display, which is valuable behavioral guidance beyond the annotations.

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 and the description is short, but the telegraphic formatting and cryptic shorthand make it harder to parse than necessary. Sentences like 'Each line: what to pass, then platforms at 2 credits a call unless numbered' are dense and unclear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with no output schema, the description covers cost rules, platform combinations, pagination, and error handling. It does not explain the shape or meaning of returned trending items, and the board-to-platform mapping remains unclear, leaving meaningful gaps for correct use.

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 adds real meaning by mapping platforms to required parameters and explaining limit and handle behavior. The shorthand 'x 6' and 'xiaohongshu 12' is ambiguous, but overall it adds useful semantics beyond 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 a platform's trending list.' It is clear enough to distinguish from generic search tools, but it does not explicitly contrast itself with siblings such as search, brand_buzz, or watch_news.

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?

It gives useful platform-specific parameter guidance, such as which platforms need no parameter and which accept type=videos or type=trends. However, it never states when to choose this tool over alternatives or when not to use it, so usage is only implied.

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