Skip to main content
Glama

BRAINIAC Social Media Content Intelligence

Repurpose content for a platform

social-content_repurpose
Read-onlyIdempotent

Shorten supplied text to a documented character limit only when the caller names a target platform. No words are added and nothing is published. Price $0.05 USDC. POST /api/v1/social-content/repurpose. 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_repurpose"
  }
}

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
limitNolimit. Number.
draftsNodrafts. Array.
statusNostatus. String.
scrapedNoscraped. Boolean.
findingsNofindings. Array.
platformNoplatform. String.
checkedAtNocheckedAt. String.
publishedNopublished. Boolean.
scheduledNoscheduled. 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 declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description still adds real value beyond them by disclosing the lossy-but-non-generative contract ('no words are added'), the $0.05 USDC cost, the POST endpoint, and the x402 payment-failure behavior where an unpaid call returns payment terms instead of running. It does not describe output shape, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and its precondition, followed by the side-effect guarantee, the price, the endpoint, and the payment failure mode. No sentence is filler and nothing is buried.

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?

With annotations and an output schema present, the description need not cover return values, and it covers cost and payment semantics well. But the tool exposes ten optional parameters and zero required ones, and the description never indicates which input field carries the text to shorten or what the posts, comments, hashtags, account, and window structures are for. That is a meaningful gap for a call this broad.

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 every parameter is already documented structurally; baseline is 3. The description adds only the notion that a platform must be named and a character limit exists, without mapping these to specific fields or explaining the roles of text, csv, file, posts, account, hashtags, and window.

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 description states a specific verb and resource: shorten supplied text to a documented character limit. That is far more concrete than the vague name 'repurpose' and clearly separates it from the analytics-oriented siblings. The slight mismatch between 'repurpose' in the name/title and 'shorten' in the description leaves a small ambiguity about whether other transformations exist, so it stops short of 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?

There is a genuine usage gate: call it only when the caller names a target platform. That is useful conditional guidance. However, no alternatives are named, and the description never explains what to do when no platform is known, nor how to choose among the ten input shapes, leaving the caller to infer the rest.

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