Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Detect engagement anomalies

social-content_engagement-anomaly-detect
Read-onlyIdempotent

Apply a Tukey 1.5 IQR fence to engagement rates when at least 8 posts have impressions and an engagement count. A point outside the fence is not a confirmed anomaly. Price $0.05 USDC. POST /api/v1/social-content/engagement-anomaly-detect. An unpaid call returns the x402 payment terms and does not run.

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": "social-content_engagement-anomaly-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
postsNoposts, array. Optional.
windowNowindow, object. Optional.
accountNoaccount, object. Optional.
commentsNocomments, array. Optional.
hashtagsNohashtags, array. Optional.
platformNoplatform, string, length 0 to 40. Optional.

Output Schema

NameRequiredDescriptionDefault
lowerNolower. Number.
postsNoposts. Array.
upperNoupper. Number.
statusNostatus. String.
scrapedNoscraped. Boolean.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
publishedNopublished. Boolean.
limitationsNolimitations. Array.
postsRemovedNopostsRemoved. Boolean.
reachInventedNoreachInvented. Boolean.
anomalyConfirmedNoanomalyConfirmed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: a $0.05 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. The minimum-sample threshold and the 'not a confirmed anomaly' caveat further set expectations about output meaning.

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?

It is short and front-loads the algorithm, followed by the sample-size condition, the interpretive caveat, then the commercial/transport details. The endpoint path is somewhat administrative, but each sentence carries distinct information with no filler.

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?

An output schema exists, so return values need no explanation, and the description covers the method, the minimum-data precondition, payment behavior, and interpretation limits. The remaining gap is that it never says which input fields constitute the 'engagement rate' or which of the several input channels to prefer for a 10-parameter optional-only schema.

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 all 10 parameters are already documented and the baseline is 3. The description adds nothing about how inputs are supplied (inline posts array vs. csv/json/text vs. file) or which fields compose the engagement rate, so it does not exceed the schema's contribution.

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 names a specific statistical operation (Tukey 1.5 IQR fence) applied to a specific resource (engagement rates), which is far more precise than a generic 'analyze' verb and naturally separates it from siblings like post-performance-analyze. It stops short of naming any sibling or stating what it is not, so it is clear but not fully differentiated.

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 gives a concrete applicability condition: at least 8 posts must have impressions and an engagement count, which tells the agent when the tool is valid. It also cautions that a point outside the fence is not a confirmed anomaly, framing how to read results. There are no explicit exclusions or pointers to alternative tools when the sample size is too small.

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.

Resources