OmniSocials

update_post_analytics

Check the X numbers of a published post again now. Works on posts published to X (refresh_not_available otherwise). The regular checks run on their own schedule (set_x_statistics); call this only when the user asks for fresh numbers of a post. At most 5 checks of a post a day (the regular checks count too) and 100 for the whole organisation (refresh_limit). x_feature_not_enabled when checking X statistics now is not enabled on the organisation's OmniSocials account (an organisation owner can enable it in OmniSocials; the numbers already stored stay); refresh_failed when X did not answer. Returns the new numbers per tweet.

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": {
      "post_id": "<post_id>"
    },
    "name": "update_post_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`post_id`	Yes	The numeric OmniSocials post id (the `id` field from list_posts). NOT a tweet id.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: per-post limit of 5 checks/day (regular checks included), 100 per organisation, plus enumerated failure codes (`refresh_not_available`, `refresh_limit`, `x_feature_not_enabled`, `refresh_failed`) and the note that stored numbers survive when the feature is disabled. It stops short of saying whether a failed check has any side effect or how quickly the new numbers appear.

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-loads the action and the eligibility constraint, then layers limits and error codes. The parenthetical about enabling X statistics is dense but each clause carries distinct operational information; only minor tightening is possible.

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 single-parameter refresh tool with no output schema, the description covers eligibility, rate limits, failure modes, and even the return shape ('new numbers per tweet'). Nothing an agent needs in order to call it correctly is missing.

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% and the schema itself already clarifies the id is the numeric OmniSocials post id from list_posts, not a tweet id. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

States a specific verb and resource ('Check the X numbers of a published post again now') and immediately scopes it to posts published to X, with `refresh_not_available` otherwise. An agent can distinguish it from get_post_analytics (stored numbers) and set_x_statistics (scheduled checks) without opening any schema.

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?

Explicitly states the default path (regular checks run on their own schedule via set_x_statistics) and the condition that selects this tool ('call this only when the user asks for fresh numbers of a post'). Both the when and the when-not are spelled out.

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?