Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Detect repeated content

social-content_duplicate-detect
Read-onlyIdempotent

Group posts whose text matches after trimming, and list pairs that share at least 90 percent of their tokens. No post is removed. Price $0.05 USDC. POST /api/v1/social-content/duplicate-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_duplicate-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
groupsNogroups. 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

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description goes well beyond that by disclosing the normalization rule (trimming), the matching threshold (90% token overlap), the pricing ($0.05 USDC), and the x402 payment handshake that causes an unpaid call to return terms instead of results. That payment/auth behavior is critical context an agent cannot infer from any structured field.

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 front-loaded sentences: what it does, the non-destructive guarantee, cost, endpoint, and the payment failure mode. Every sentence carries information, though the raw POST path is of marginal value to an agent compared to the algorithm and payment details.

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?

The output schema exists, so return-shape explanation is correctly omitted, and the payment model is fully covered. For a tool with ten optional parameters, nested objects, and multiple interchangeable input formats, the definition leaves an agent without any instruction on how to construct the request payload, which is the main unresolved gap.

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, but the schema descriptions are mechanical ('csv, string, length 0 to 200000. Optional.') and do not convey meaning. The description adds nothing about the ten parameters, leaving a real gap: five alternative input channels (csv, file, json, text, posts) and no statement of precedence or mutual exclusivity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise operation ('group posts whose text matches after trimming', 'list pairs sharing at least 90 percent of tokens'), which defines duplicate detection far beyond what the name conveys. The two output shapes (grouped posts and matched pairs) are both named, so an agent knows exactly what it gets back.

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 frames this as a non-destructive analysis ('No post is removed'), which implies an appropriate use case, and it names the payment precondition. However, it gives no explicit when-to-use versus siblings such as social-content_engagement-anomaly-detect or social-content_post-performance-analyze, and no guidance on which input channel (posts, csv, json, text, file) to supply.

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