Skip to main content
Glama
social-watch-mcp

social-watch-mcp

by denis1stomin

totals

Read-only

Retrieve account-level metrics for Threads, itch.io, YouTube, or X, including followers, total views, downloads, and purchases.

Instructions

Account-level numbers: followers, total views, downloads, purchases...

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": "totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesOne of: threads, itch, youtube, x

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns account-level metrics such as followers, views, downloads, and purchases, but it does not explain timeframe, aggregation behavior, or what happens per platform. With annotations carrying the safety burden, a 3 is appropriate.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted preamble. However, the trailing ellipsis leaves the list of metrics open-ended, which slightly undermines precision.

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?

The tool is simple, with one required parameter fully described in the schema and clear read-only annotations. But with no output schema, the description should do more to clarify the returned totals, such as whether they cover a time range or how platform affects the metrics, and the ellipsis leaves that incomplete.

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% and the single platform parameter is fully documented with an enum, so the schema does the heavy lifting. The description does not mention the platform parameter or add any meaning beyond what the schema already provides, making baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('account-level numbers') and gives example metrics, but it lacks a clear action verb and never distinguishes this tool from siblings such as post_stats or accounts. An agent can infer it retrieves aggregate account metrics, but the purpose is only moderately clear.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives like post_stats, replies, accounts, or recent_posts. The phrase 'account-level' implies aggregate usage, but no exclusions, prerequisites, or sibling routing are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools