Skip to main content
Glama

Configurar o Puxador

set_userbot_config
Destructive

Altera a configuração do módulo Puxador. Envie só o que quer mudar: settings (enabled, approvalGroupId, defaultDestinationId, blocklist, textSource, photoSource, autoShowcase, autoApprove, approvalMode), channel (channelId + title/rules/destinationChannelId/enabled/autoApprove), rule (roteamento por palavra-chave ou nº de links, com autoApprove) ou deleteChannelId/deleteRuleId. Aprovação automática: precedência regra > canal > global; em canal e regra, autoApprove null herda, 1 sempre, 0 nunca. Ligar (true/1) exige o aceite do termo, que só o dono dá no painel (Puxador › Configuração › Aprovação automática): sem ele a chamada falha com auto_approve_consent_required — peça ao usuário para aceitar lá; este tool não aceita por ele. Em channel.rules.converter, escolha um perfil de TEXTO da origem: economizandoComJP, economizanderson, ofertasBenevides, linksBR, promoChinaOfertas, setupHumilde, samuelFelipe, promoBugs ou promotom; string vazia remove o perfil. Isso não escolhe o conversor de link afiliado: links continuam seguindo globalmente o domínio nas abas Rotas e Plugins do bot. Exemplo de channel.rules: { "converter": "promotom", "replacements": [{ "find": "-CUPOM:", "replace": "🏷 Cupom:", "isRegex": false }], "discardIfContains": ["palavra proibida"] }. Dica: valide com preview_userbot_rules antes de salvar.

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

Input Schema

NameRequiredDescriptionDefault
ruleNoRegra de roteamento (cria, ou atualiza se mandar id).
channelNoCanal monitorado (cria ou atualiza pelo channelId).
settingsNoSettings do módulo (parcial).
deleteRuleIdNoID da regra de roteamento a apagar (de get_userbot_config). Apaga de vez: confirme com o usuário.
deleteChannelIdNoID do canal monitorado a apagar (de get_userbot_config). Apaga de vez: confirme com o usuário.

Output Schema

NameRequiredDescriptionDefault
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes well beyond them: the auto-approval consent gate and its exact error code, the inheritance precedence rule > channel > global, and the clarification that channel.rules.converter selects a text profile and does NOT change affiliate-link conversion (which stays governed by Rotas/Plugins). That last point is a real side-effect boundary an agent could otherwise get wrong.

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?

Well front-loaded: what it does, then partial-update rule, then the consent gotcha, then the converter caveat, then an example and a tip. Dense but every block is actionable. The one waste is restating all nine converter profile names that the schema enum already lists.

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?

For a 5-param nested mutation tool with an output schema and full annotation coverage, the description covers the residual risk surface: consent failure mode, precedence resolution, irreversible deletes, and the scope boundary of the converter field. Nothing an agent needs to call this safely is missing.

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 schema already carries per-field meaning; the description nonetheless adds cross-parameter semantics the schema cannot express — the three-level autoApprove precedence and the null/1/0 inheritance behavior. It also supplies a worked channel.rules example with replacements and discardIfContains. Slight deduction because the converter profile list is duplicated verbatim from the enum description.

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?

Opens with a specific verb+resource ("Altera a configuração do módulo Puxador") and immediately defines the four mutation surfaces (settings, channel, rule, delete*). It distinguishes itself from preview_userbot_rules by pointing at it as a validation step, but never explicitly contrasts with get_userbot_config for reading current state, leaving that routing to the schema.

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?

Explicitly states the partial-update contract ("Envie só o que quer mudar"), gives a concrete when-to-use-before (validate with preview_userbot_rules), and names the failure condition with a remedy path when consent is missing (auto_approve_consent_required → ask the user to accept in the panel; this tool cannot do it). Deletions are flagged as irreversible with an instruction to confirm first.

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