OmniSocials

set_x_statistics

DestructiveIdempotent

Choose how often the posts of an X account are checked (full = 5 checks: about 5 hours after publishing, day 1, 3 and 7, and day 30 for posts with 100+ views; light = 2 checks: about 5 hours and day 7; off) and how often its followers are counted (daily, weekly, off). Send posts, followers or both; a value left out stays as it is. Tell the user what the choice means and ask before calling. X accounts only (the account id ends in _x). Changing it needs the organisation owner or an admin of the organisation (an API key also needs the opt-in accounts:write scope, set when the key is made). list_accounts and get_account show the current setting.

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": {
      "account_id": "<account_id>"
    },
    "name": "set_x_statistics"
  }
}

Input Schema

Name	Required	Description
`posts`	No	How often each post is checked: full = 5 checks (about 5 hours, day 1, 3 and 7, and day 30 for posts with 100+ views), light = 2 checks (about 5 hours and day 7), off = no checks.
`followers`	No	How often the account's followers are counted: daily, weekly or off.
`account_id`	Yes	The X account id from list_accounts, the Channel ID that ends in `_x` (for example `1234_x`).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds real context on top: the required role (organisation owner or admin) and the accounts:write API key scope. It also adds confirmation guidance before mutating. The one gap is that it never explains why the operation is destructive — e.g. whether setting `off` discards or stops collecting existing statistics.

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?

Front-loaded with the action and its option meanings, then eligibility, permissions and confirmation. It is a single dense paragraph with mild redundancy, since the full/light check cadences are repeated from the enum descriptions; those words could be trimmed without loss.

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 three-parameter mutation with no output schema, the description covers everything an agent needs: eligibility, permission and scope requirements, partial-update semantics, confirmation behaviour, and where to read the current value. Nothing material is missing.

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?

Schema coverage is 100% and both enums are fully documented, so the baseline is 3. The description adds the partial-update rule ('a value left out stays as it is'), which is not expressed anywhere in the schema and materially changes how the agent should call it.

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

Purpose5/5

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

The description opens with a specific verb and resource: it configures how often an X account's posts are checked and its followers counted, with the exact cadences enumerated. No sibling tool does this, and the scope is bounded explicitly to X accounts (ids ending in `_x`).

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

Usage Guidelines5/5

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

It states what to send (posts, followers, or both), that omitted values are left unchanged, and instructs the agent to explain the choice and ask the user before calling. It also points to list_accounts and get_account for reading the current setting, so both the action and the read alternative are routed.

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

All OmniSocials tools Inspect

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

Need Help?