Skip to main content
Glama

Listar campanhas

list_campaigns
Read-only

Lista as campanhas de captação do workspace (Telegram e WhatsApp) com total de grupos, grupos abertos (com vaga e saudáveis), membros e link público. Use quando o usuário perguntar "como estão minhas campanhas", quiser ver quais existem ou precisar de um id/slug para as outras tools.

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

Input Schema

NameRequiredDescriptionDefault
canalNoOpcional. Só campanhas desse canal de destino.
limiteNoMáximo de campanhas (1 a 100; padrão 50).
statusNoFiltro: "ativas" (padrão), "arquivadas" ou "todas".ativas

Output Schema

NameRequiredDescriptionDefault
itensNoCampanhas.
totalNo
successNo
has_moreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by explaining what a campaign record actually contains, including derived health signals like open groups with vacancies. It does not cover rate limits, ordering, or pagination behavior beyond the limite parameter.

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?

Two sentences, no filler: the first defines the resource and return contents, the second covers the usage triggers. Scope and purpose are front-loaded before the conditional guidance.

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

Completeness4/5

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

An output schema exists, so return values needn't be explained, and the three optional filters are fully documented in the schema. The only gap is that the description doesn't mention the default of showing only active campaigns, which affects what the agent will actually get back.

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%, with each parameter documented including enum values and the default of 50. The description adds no information about the canal, status, or limite filters, so the baseline 3 applies.

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 specific verb and resource ('Lista as campanhas de captação do workspace') and additionally specifies the channels covered and the fields returned (totais de grupos, grupos abertos com vaga, membros, link público). This is enough to distinguish it from get_campaign, campaign_metrics, and the group-listing siblings.

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

Usage Guidelines4/5

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

Gives three concrete triggers: when the user asks 'como estão minhas campanhas', wants to see which campaigns exist, or needs an id/slug for other tools. That last clause usefully routes the agent toward the follow-up tools. No explicit when-not or named alternative, so a 4 rather than a 5.

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