Skip to main content
Glama

Account snapshot

account_watch
Read-only

What a set of accounts published lately and which posts did clearly better than each account's usual. It runs once. Runs on our side. A costly or long run quotes its price first. To repeat it daily, use watch. Credits by scale small/medium/large, for one account: bilibili, youtube 10/12/22; douyin, reddit, weibo, zhihu 10/14/24; kuaishou 30/54/70; wechat 42/90/120; x 9/13/29; xiaohongshu 30/54/84; facebook 12/20/30; instagram 12/18/28; linkedin 12/20/-; telegram 10/14/-; threads 12/16/-; tiktok 12/20/36; wechat_channels 42/66/96. 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": {
      "accounts": "<accounts>"
    },
    "name": "account_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoPer account: small about 20 posts, medium about 60, large as medium and the comments of 2 posts that took off.
handleNoA handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run.
windowNoHow far back to look for new posts. One of 7d, 30d.
confirmNotrue: run it whatever it costs. false: answer the plan and its price, and run nothing. Left out: a costly run, and one that runs in the background, answers its price first.
accountsYes1 to 20 links to account pages; they may be of different platforms.
max_cost_creditsNoRefused, free, with the quote, if the run would cost more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, non-idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: server-side execution, upfront cost quoting for expensive runs, per-platform/per-scale credit pricing, and 'follow error.fix' remediation. That is substantial added context, but the dense credit table is cost reference rather than behavioral disclosure, so it lands at solid-but-not-maximal.

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 first three sentences are front-loaded and earn their place, but the multi-line credit table dominates the text and is reference data rather than guidance, which hurts scannability. Information density is high with no wasted words, yet the layout favors completeness over concision.

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?

With no output schema, the description still conveys what comes back (recent posts plus outlier posts) and surfaces billing.display, which is enough for an agent to act. The handling of the handle/confirm interaction is coherent with the schema, though the relationship between handle and a fresh accounts run could be stated more explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all six parameters including scale, handle, window and confirm. The description adds only two small pieces of meaning beyond it: 'Pass links whole, as given' for accounts and the instruction to surface billing.display to the user. Baseline 3 applies given the schema does the heavy lifting.

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 opening sentence names the resource (a set of accounts' recent posts) and the analytical output (posts that beat each account's usual), which is specific and not tautological with the title. It also explicitly contrasts itself with the sibling 'watch' tool. The phrasing is noun-phrase rather than verb-led, so the agent must infer the operation, but the outcome is unambiguous.

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

Usage Guidelines4/5

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

It clearly states this is a one-shot run and routes recurring use to 'watch', and it explains the confirm/quote decision flow for costly runs. It does not distinguish itself from other per-account siblings like 'account' or 'user_posts', leaving some sibling selection to inference.

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.