Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Analyze post performance

social-content_post-performance-analyze
Read-onlyIdempotent

Calculate engagement and an engagement rate from supplied impressions, likes, comments, shares, and saves. A missing count is left out, and no rate is calculated without impressions. Equal rates keep the caller's input order. Price $0.04 USDC. POST /api/v1/social-content/post-performance-analyze. 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_post-performance-analyze"
  }
}

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
postsNoposts. Array.
statusNostatus. String.
scrapedNoscraped. Boolean.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
publishedNopublished. Boolean.
limitationsNolimitations. Array.
postsRemovedNopostsRemoved. Boolean.
reachInventedNoreachInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely non-obvious behavior: missing counts are dropped rather than zero-filled, impressions gate rate calculation, equal rates preserve input order, and an unpaid call returns x402 payment terms without executing. The one gap is that it doesn't describe the shape or units of the returned rate, though an output schema exists for that.

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 calculation behavior is front-loaded in the first sentence and the remaining sentences each carry a distinct rule. The pricing and endpoint sentences are terse but slightly crowd out input-shape guidance, keeping it short of a 5.

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?

For a tool with ten optional top-level parameters, multiple alternate input formats, and nested objects, the description covers output semantics and payment gating but says nothing about how to choose between structured 'posts' and the csv/json/text/file payloads. Since an output schema exists, the missing return-value description is not a defect; the input-mode ambiguity is.

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 the baseline is 3. The description does add semantic value by naming the metric fields it consumes and stating that omitted counts are excluded rather than treated as zero, but it never explains the relationship among the ten top-level inputs (posts vs. csv/json/text/file vs. window/account), which is the real ambiguity in this schema.

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 first sentence names a specific verb (calculate) and specific outputs (engagement and engagement rate) plus the exact input metrics, so the operation is unmistakable. It does not, however, differentiate itself from siblings such as account-performance-report or hashtag-analyze, leaving the agent to infer which analysis scope applies.

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

Usage Guidelines3/5

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

Usage is only implied: 'from supplied impressions, likes, comments, shares, and saves' tells the agent what data must be on hand, and 'no rate is calculated without impressions' sets a precondition. There is no explicit when-to-use versus the sibling reporting/analysis tools, and no statement of when this tool is the wrong choice.

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