Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Classify supplied comments

social-content_comment-classify
Read-onlyIdempotent

Match a supplied type to question, praise, complaint, spam, or request. Without a type, a comment is labeled only when one documented keyword rule matches. No moderation action is taken. Price $0.03 USDC. POST /api/v1/social-content/comment-classify. 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_comment-classify"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well past the annotations by disclosing pricing ($0.03 USDC), the x402 payment handshake, and that an unpaid call returns payment terms without executing. It also clarifies that a comment without a supplied type is labeled only when one documented keyword rule matches, and that no moderation action is taken — meaningful behavioral context for an otherwise read-only, idempotent tool.

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 classification behavior, then layers in the fallback rule, the no-moderation guarantee, and the payment mechanics in a compact sequence. The endpoint path and price sentences are operationally useful rather than filler, though the payment detail is stated twice in effect.

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?

Ten parameters with nested objects and an output schema, so the description only needs to carry semantics — which it largely does, covering classification behavior, the type-less path, side-effect freedom, and billing. The gap is input precedence and expected batching behavior, which an agent must infer from the schema alone.

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 top-level parameters including the nested comment `type` field. The description adds one useful semantic point — how the `type` value drives matching and what happens when it is absent — but says nothing about which content source (csv, file, json, text, posts) takes precedence when several are supplied.

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?

States a specific verb and outcome — match a supplied type to one of five labels (question, praise, complaint, spam, request) for comments. The resource and taxonomy are unambiguous, though it never explicitly contrasts itself with siblings such as post-performance-analyze.

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?

Implies the use case (labeling comments rather than moderating them) and explains the fallback path when no type is supplied. It does not say when to prefer this over, say, engagement-anomaly-detect, nor what input shape is expected for batch vs single-comment classification.

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