Skip to main content
Glama

Petits comptes viraux (recommandés)

petits_comptes_viraux

Find viral posts from small accounts (≤50k followers) that reached ≥300k views, ranked by views-to-follower ratio to reveal reproducible formats that work without an audience.

Instructions

Les recommandés de viraldar : des posts de comptes ≤ 50 k abonnés qui ont fait ≥ 300 k vues et ≥ 20 × leurs abonnés, classés par vues ÷ abonnés, 2 au plus par compte, les 100 premiers — les formats qui marchent sans audience, donc les plus reproductibles. Mêmes filtres que chercher_posts (thèmes, mes_themes, langue, mots…). Les posts déjà gardés ou passés par l'utilisateur n'y sont plus. 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": "petits_comptes_viraux"
  }
}

Input Schema

NameRequiredDescriptionDefault
motsNoTous ces mots, dans le texte, le compte ou les mots-clés (accents ignorés).
pageNo0 = première (24 posts) ; chaque post neuf compte dans le quota.
detailNoToutes les stats, texte entier.
formatNo
themesNoClés de thèmes (infos_base), l'un OU l'autre.
languesNo
likes_okNoLikes ≥ 2 % des vues (sinon souvent de la pub).
vues_minNo
mes_themesNoAjoute les thèmes de l'utilisateur.
abonnes_maxNo
demande_appNo📲 : des commentaires demandent le nom de l'app.
outlier_minNovues ÷ médiane du compte, minimum (ex. 5).
publie_depuis_joursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Since no annotations are provided, the description carries the full burden and does so exceptionally well. It outlines crucial behavioral constraints, including the specific ranking metric (views $\div$ followers), the exclusion of previously viewed posts, and the impact on the daily quota.

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?

Despite the dense information load, the text is extremely concise and efficient. It packs statistical criteria, operational limits, and cross-tool references into a single, well-structured paragraph without any filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is highly complete for a specialized retrieval tool. It addresses both the logical constraints (views $\div$ followers) and the operational constraints (daily quota, post limits), giving the agent all necessary context to call the tool accurately.

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?

With schema coverage at 62%, the baseline score of 3 is appropriate. The description helps by confirming it uses the same filtering parameters as `chercher_posts`, providing context, but does not semantically elaborate on the meaning of individual complex parameters like `outlier_min` beyond the tool's stated purpose.

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?

The description clearly defines a highly specific niche: finding viral post formats from micro-accounts (under 50k followers) that demonstrate extreme engagement relative to their size. This immediately distinguishes it from a general search tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides excellent usage guidelines by comparing itself to `chercher_posts` and stating that this tool should be used when seeking reproducible formats from smaller audiences. It also includes operational usage rules, such as the limit of 2 posts per account and daily quota tracking.

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