Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Formats viraux similaires

formats_similaires

Finds TikTok posts sharing hashtags with a reference post or tag list, filters by similar duration, and ranks high outliers to help replicate a proven format.

Instructions

Des posts de la base qui partagent le plus de hashtags avec un post (ou avec une liste de hashtags), puis de durée proche (± 50 %), puis le plus haut outlier ; 24 au plus, 2 par compte. Pour décliner un format qui marche. Compte dans le quota du jour.

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": "formats_similaires"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNoId ou URL d'un post déjà vu : ses hashtags et sa durée servent de modèle.
detailNo
duree_sNoDurée de référence en secondes (vidéos).
hashtagsNoSinon, des hashtags (sans #) ou mots.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the ranking pipeline (hashtags → duration ±50% → outlier score), the result caps (24 max, 2 per account), and that the call consumes the daily quota ('Compte dans le quota du jour'), which is operationally important for an agent. It does not discuss auth or return shape, but the quota and cap disclosures are substantive beyond what structured data provides.

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?

Dense but front-loaded: the ranking criteria come first, then the caps, then the purpose, then the quota note. Every clause carries information. The telegraphic fragment style (missing verb, semicolon-chained limits) costs a bit of readability.

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?

For a read/search tool the description covers selection logic, caps, and quota consumption, which is most of what an agent needs to call it. The notable gap is the `detail` parameter, undocumented in both schema and description, and there is no indication of what fields each returned post carries (no output schema exists).

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 75%, and the description meaningfully clarifies the two input modes: a reference post ('ses hashtags et sa durée servent de modèle') or, alternatively, a hashtag list ('Sinon, des hashtags'). It also ties the duration criterion to the ±50% window, adding interpretation beyond the schema. The `detail` boolean remains undocumented in both places.

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 names the resource (posts from the database) and states the exact selection criteria: most shared hashtags, then duration within ±50%, then highest outlier. An agent can tell this apart from a generic search such as chercher_posts. It lacks an explicit verb (it opens with a noun phrase, 'Des posts de la base qui...'), which slightly weakens the statement of action.

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 phrase 'Pour décliner un format qui marche' gives a clear intended use case, which is real guidance. However, no alternative is named and no when-not condition is given, so the agent must infer on its own whether to use this instead of siblings like a_reproduire or chercher_posts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools