Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Analyze supplied hashtags

social-content_hashtag-analyze
Read-onlyIdempotent

Count hashtags in the supplied posts and copy post and impression figures from supplied hashtag rows. The counts stay separate. Current popularity and reach are not estimated. Price $0.04 USDC. POST /api/v1/social-content/hashtag-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_hashtag-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
statusNostatus. String.
scrapedNoscraped. Boolean.
findingsNofindings. Array.
hashtagsNohashtags. Array.
checkedAtNocheckedAt. String.
publishedNopublished. Boolean.
limitationsNolimitations. Array.
postsRemovedNopostsRemoved. Boolean.
reachInventedNoreachInvented. 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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive context on top: a $0.04 USDC price, the POST route, and the crucial note that an unpaid call returns x402 payment terms and does not execute. It also discloses that counts stay separate and that popularity/reach are not estimated. Only the response shape is left unaddressed, which the output schema covers.

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?

Short, front-loaded sentences with no filler; the counting behavior comes first and the payment mechanics last. The telegraphic phrasing ('The counts stay separate') is slightly compressed but never ambiguous.

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?

Payment behavior, computational limits, and copy semantics are all covered and an output schema exists, so the core is sound. However, for a 10-parameter tool with four interchangeable-looking text inputs (csv, json, text, file) plus a nested posts array, the description says nothing about which input form to supply or how they relate, leaving a real selection gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds genuine meaning by clarifying that hashtag rows are a source of post and impression figures that are copied rather than computed. It does not explain the role of the csv/json/text/file alternatives among the 10 parameters, which keeps it below a 5.

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 resource: count hashtags in the supplied posts and copy post/impression figures from supplied hashtag rows. The word 'supplied' is doing real work, signaling this is an analysis of user-provided data rather than a live fetch, which separates it from siblings like post-performance-analyze. It never names a sibling explicitly, so it stops short of a 5.

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 implies the caller must bring their own posts and hashtag rows, and it rules out popularity/reach estimation, which is useful scoping. But there is no explicit when-to-use guidance, no named alternative, and no statement of what input combination is expected, so the agent must infer the scenario.

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