Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Report account performance

social-content_account-performance-report
Read-onlyIdempotent

Combine supplied totals, platform splits, calendar slots, drafts, hashtags, comments, rate fences, and repeated text. The report does not publish content or estimate reach. Price $0.12 USDC. POST /api/v1/social-content/account-performance-report. 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_account-performance-report"
  }
}

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.
slotsNoslots. Array.
draftsNodrafts. Array.
groupsNogroups. Array.
statusNostatus. String.
scrapedNoscraped. Boolean.
commentsNocomments. Array.
findingsNofindings. Array.
hashtagsNohashtags. Array.
unplacedNounplaced. Array.
anomaliesNoanomalies. Array.
checkedAtNocheckedAt. String.
followersNofollowers. Number.
postCountNopostCount. Number.
publishedNopublished. Boolean.
scheduledNoscheduled. Boolean.
byPlatformNobyPlatform. Array.
engagementNoengagement. Number.
accountNameNoaccountName. String.
averageRateNoaverageRate. Number.
impressionsNoimpressions. Number.
limitationsNolimitations. Array.
commentCountNocommentCount. Number.
postsRemovedNopostsRemoved. Boolean.
reachInventedNoreachInvented. Boolean.
accountPlatformNoaccountPlatform. String.
anomalyConfirmedNoanomalyConfirmed. Boolean.
moderationActionNomoderationAction. Boolean.
averageCalculatedNoaverageCalculated. Boolean.
followersSuppliedNofollowersSupplied. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses real operational context: the $0.12 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms and does not execute. That last point is behavior an agent cannot learn from annotations or schema, and it prevents a silent no-op failure.

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?

Four short sentences, front-loaded with the combine operation before moving to scope limits, pricing, and endpoint. The opening inventory is somewhat dense and reads like a feature list rather than a sentence, but nothing is redundant.

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?

With an output schema present, return values need no explanation, and the description covers the remaining gaps an agent needs: it is a read/analysis operation that publishes nothing, it costs money, and unpaid invocations short-circuit. For a ten-parameter nested-input tool, that is sufficient to call it correctly.

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 schema already documents all ten parameters and their nested shapes, establishing a baseline of 3. The description's list (totals, platform splits, calendar slots, drafts, hashtags, comments) loosely gestures at the domain meaning of posts/comments/hashtags/account but does not clarify how csv/json/text/file alternate inputs relate to each other or which combination is expected.

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?

"Combine supplied totals, platform splits, calendar slots, drafts, hashtags, comments, rate fences, and repeated text" names the operation and the input dimensions it consolidates, and the negative clause "does not publish content or estimate reach" carves out scope versus content-producing siblings. It stops short of naming a specific sibling such as post-performance-analyze, so differentiation is only partial.

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?

The description gives implicit guidance through exclusions ("does not publish content or estimate reach") and by noting the inputs are supplied rather than fetched, which implies a caller-assembled dataset. There is no explicit "use this when / use X instead" routing against the seven siblings, so an agent must infer the selection criteria.

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