Skip to main content
Glama
social-watch-mcp

social-watch-mcp

by denis1stomin

accounts

Read-only

Retrieve configured social platforms and profile details—name, handle, and follower or subscriber counts—for Threads, itch.io, YouTube, or X.

Instructions

Which platforms are set up, and each profile (name, handle, followers/subscribers where the API gives them).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoOne of: threads, itch, youtube, x

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral caveat — follower/subscriber counts appear only 'where the API gives them' — which tells the agent to expect optional or missing fields. It does not explain the platform scoping behavior or the response shape, so the added context is thin but real.

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?

One compact sentence with the payload description front-loaded and no filler. It reads as a sentence fragment rather than a directive verb phrase, which slightly weakens the lead.

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 only one optional parameter, annotations present, and no output schema, the description does the important work of describing return content: platforms plus per-profile name, handle, and audience counts. The one substantive omission is the effect of the platform argument, which is the main thing an agent could get wrong.

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 coverage is 100% with a single optional enum parameter fully documented, so the baseline of 3 applies. The description never mentions the platform filter, leaving ambiguous whether passing it narrows the list or fetches one account, which is a missed opportunity rather than a schema gap.

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 description states the resource clearly: it enumerates which platforms are connected and returns each profile's name, handle, and follower/subscriber counts. That is specific enough for an agent to know it is an account-inventory call. It does not, however, contrast itself with siblings like totals or post_stats, so the differentiation must be inferred from the surrounding tool names.

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 statement of when to use this tool versus totals or recent_posts, nor any prerequisite or exclusion. The phrase 'where the API gives them' hints at data gaps but is not framed as usage guidance. An agent must infer that this is the discovery step before other platform calls.

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