Skip to main content
Glama
Sign In

SocialToAI

by com.socialtoai
OverviewDiscussionsAdmin

Search content

search
Read-only

Search a platform for content. 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). Give query: bilibili, douyin 12, kuaishou 12, linkedin, pinterest, reddit, threads, tiktok, wechat 12, wechat_channels 12, weibo, x, xiaohongshu 12, youtube, zhihu With type=user: douyin, instagram 3, kuaishou 12, tiktok, wechat 102, wechat_channels 36, weibo, x 5, xiaohongshu 12, youtube, zhihu With sort=latest: x With type=image: xiaohongshu 12 since/until: ISO dates, all platforms. More parameters: capabilities. On error, follow error.fix. Tell the user billing.display.

Input Schema

NameRequiredDescriptionDefault
sortNoBy platform: relevance, latest, popular
typeNoAnswers only, or articles only; both when left out. By platform: answer, article, user, image
queryNo
sinceNoPublished at or after: an ISO 8601 date (2026-10-01) or time. Where the platform has no such filter, its nearest time window is used and the page is filtered by published_at; warnings say so.
untilNoPublished at or before: an ISO 8601 date (that whole day) or time. Where the platform has no such filter, the page is filtered by published_at; warnings say so.
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.
max_cost_creditsNoRefused, free, if the call would cost more.
published_withinNoBy platform: day, week, half_year, month, year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / query / description
      Removed value: -"Search terms"
  2. Changed2 schema fields changed
    • changedInput schema / properties / since / description
      Previous value: -"Published on or after this day (filtered by UTC date; the time of day is ignored)"New value: +"Published at or after: an ISO 8601 date (2026-10-01) or time. Where the platform has no such filter, its nearest time window is used and the page is filtered by published_at; warnings say so."
    • changedInput schema / properties / until / description
      Previous value: -"Published on or before this day (filtered by UTC date; the time of day is ignored)"New value: +"Published at or before: an ISO 8601 date (that whole day) or time. Where the platform has no such filter, the page is filtered by published_at; warnings say so."
  3. Changed1 schema field 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."
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description provides critical operational context beyond the structured data, specifically detailing the cost model ('platforms at 2 credits a call unless numbered') and failure rates ('Failed calls cost 0'). This is invaluable behavioral information that the schema does not cover.

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

Conciseness1/5

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

The description is extremely dense, disorganized, and reads like a mashup of internal developer notes and usage examples rather than a clean, concise description. The core purpose is fragmented across multiple sentences, and the critical information is not front-loaded.

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?

Despite the poor structure, the description is functionally complete. It covers operational constraints, usage syntax, and specific platform limitations, providing all necessary information to execute the tool successfully.

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?

While the schema is detailed (90% coverage), the description clarifies the practical application of parameters, especially within the context of specific platform filtering and structured usage examples (e.g., how specific platform names translate into query parameters).

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 purpose is stated clearly in the title and opening line ('Search a platform for content'). However, the description quickly transitions into highly operational and instructional language, making the core function slightly obscured by surrounding details.

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

Usage Guidelines5/5

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

This is a prime example of excellent usage guidance. It provides concrete, practical examples of how to construct calls (e.g., 'Give query: bilibili, douyin 12') and demonstrates use cases for different parameters like 'With type=user:' or 'With sort=latest:'. This is highly actionable for an agent.

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