Skip to main content
Glama
Sign In

SocialToAI

by com.socialtoai
OverviewDiscussionsAdmin

Get content details

detail
Read-only

Get one piece of content by its id or link. 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. Give id|url: bilibili, douyin, instagram, kuaishou, linkedin, pinterest, reddit, telegram, threads, tiktok, weibo, x 1, xiaohongshu 12, youtube, zhihu Give url: facebook, wechat 12 Give id|url|export_id: wechat_channels 12 With type=article|pin|question: zhihu Add include=transcript, charged on top: instagram, linkedin, reddit, tiktok, x, youtube More parameters: capabilities. Pass links whole, as given. On error, follow error.fix. Tell the user billing.display.

Input Schema

NameRequiredDescriptionDefault
idNo
urlNo
typeNoBy platform: article, pin, question
handleNoA handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run.
includeNoFetched beside each result: transcript.
platformYesOne, or a list.
export_idNoThe id of a search (platform=wechat_channels) result, starting with export/. It expires: use it soon after the search. The id returned is the video's numeric ID
max_cost_creditsNoRefused, free, if the call would cost more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / export_id
      Added value: +{
+  "description": "The id of a search (platform=wechat_channels) result, starting with export/. It expires: use it soon after the search. The id returned is the video's numeric ID",
+  "type": [
+    "string",
+    "array"
+  ]
+}
  2. 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."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile, yet the description adds real value: per-call cost (2 credits unless numbered), 'Failed calls cost 0', the max_cost_credits refusal behavior, and the error.fix recovery instruction. It also tells the agent to relay billing.display. That is substantive behavior beyond the annotations, though return-shape detail is thin.

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 and read-only note are front-loaded, which is good, but the body is a dense, telegraphic block of platform lists where numbers like '12' must be inferred as credits. Every line is relevant, yet the compressed formatting costs parseability.

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 an 8-parameter tool with no output schema, the description covers billing, per-platform input requirements, optional extras, error recovery, and user-facing messaging. The main gap is the shape of the returned content line, which is only gestured at with 'Each line: what to pass'.

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 75% schema coverage the baseline is 3, and the description exceeds it by mapping accepted input forms per platform (id|url vs url-only vs id|url|export_id), scoping type to zhihu, and restricting include=transcript to specific platforms. The 'a|b' notation and bare numbers ('x 1', 'xiaohongshu 12') are terse enough to require interpretation, keeping it from 5.

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: 'Get one piece of content by its id or link,' plus 'Read-only.' That clearly separates it from list-oriented siblings like search, user_posts, and comments. It doesn't explicitly name a sibling alternative, so it stops short of 5.

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?

Gives operational guidance such as 'A list of platforms, ids or links: a call each' and 'Pass links whole, as given,' which implies when and how to call. However, it never says when to prefer this over user_posts or comments, nor what prerequisites exist beyond per-platform input forms.

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