Skip to main content
Glama

List an account's posts

user_posts
Read-only

List what one account has published. Read-only. Each line: what to pass (a|b: either one), 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 id: bilibili, kuaishou 12, wechat 12, wechat_channels 12, weibo Give id|url: douyin, xiaohongshu 12 Give id|username|url: facebook Give username: instagram, reddit, telegram, threads, tiktok, x, zhihu Give username|url: linkedin Give id|username: youtube With type=answer|pin: zhihu More parameters: capabilities. Pass links whole, as given. On error, follow error.fix. Tell the user billing.display.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>"
    },
    "name": "user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
tabNoOnly wechat, x. By platform: articles, videos, images, posts, replies, media
urlNo
sortNoOnly tiktok, youtube. By platform: latest, popular
typeNoOnly instagram, youtube, zhihu. By platform: all, reel, video, short, answer, pin
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.
usernameNo
max_cost_creditsNoRefused, free, if the call would cost more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / sort / description
      Previous value: -"By platform: latest, popular"New value: +"Only tiktok, youtube. By platform: latest, popular"
    • changedInput schema / properties / tab / description
      Previous value: -"By platform: articles, videos, images, posts, replies, media"New value: +"Only wechat, x. By platform: articles, videos, images, posts, replies, media"
    • changedInput schema / properties / type / description
      Previous value: -"By platform: all, reel, video, short, answer, pin"New value: +"Only instagram, youtube, zhihu. By platform: all, reel, video, short, answer, pin"
  2. Changed1 schema field changed
    • changedInput schema / properties / tab / description
      Previous value: -"Which tab of the profile: posts (retweets among them), replies (with the posts replied to), or media. By platform: posts, replies, media"New value: +"By platform: articles, videos, images, posts, replies, media"
  3. Changed2 schema fields changed
    • changedInput schema / properties / sort / description
      Previous value: -"Newest first, or most popular first. By platform: latest, popular"New value: +"By platform: latest, popular"
    • changedInput schema / properties / type / description
      Previous value: -"Every post, or reels only. By platform: all, reel, answer, pin"New value: +"By platform: all, reel, video, short, answer, pin"
  4. 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."
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description correctly reinforces read-only. Beyond that it adds real behavioral context the annotations do not carry: per-platform credit cost (2 credits a call), failed calls cost 0, max_cost_credits refusal, free re-reads via handle/cursor, and an error/billing protocol (error.fix, billing.display).

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 flag are correctly front-loaded, but the body is a dense shorthand block ("Each line: what to pass (a|b: either one)") that requires parsing, and it mixes cost rules, identifier rules and pagination in one run without grouping. It is compact but cryptic rather than efficient.

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

Completeness5/5

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

For a 10-parameter, multi-platform, no-output-schema tool this is close to complete: caller identity requirements per platform, cost model, pagination, error handling and billing disclosure are all covered. The only real defect is the phantom limit=100 reference, which should have been cursor/paging language instead.

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 70% schema coverage the baseline is 3, and the description genuinely adds meaning: it maps which of id/url/username each platform accepts, and restricts type to zhihu answer|pin and tab to wechat/x. Offsetting that, it never clarifies sort, max_cost_credits or array-valued platform, and it references an undocumented limit parameter.

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?

"List what one account has published" gives a specific verb and resource, and the platform matrix makes the scope concrete (one account, many platforms). It never names a sibling (user_profile, comments, detail) to contrast with, so an agent must infer that this is the per-account post lister rather than a search tool.

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 effectively tells the agent which identifier to supply per platform (id vs username vs url) and adds practical rules (100 items via limit=100, failed calls are free, stop on error.fix). But there is no when-not-to-use guidance and no alternative named, and "limit=100" refers to a parameter that does not exist in the schema, which misleads rather than guides.

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.