Skip to main content
Glama

List campaigns

list_campaigns
Read-onlyIdempotent

List the campaigns of this account with their inbox, schedule and status. Call before changing or deleting one.

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
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "id",
      -  "title",
      -  "description",
      -  "message",
      -  "enabled",
      -  "campaign_type",
      -  "campaign_status",
      -  "scheduled_at",
      -  "trigger_only_during_business_hours",
      -  "audience",
      -  "inbox"
      -]New value: +[
      +  "id",
      +  "title",
      +  "description",
      +  "message",
      +  "enabled",
      +  "campaign_type",
      +  "campaign_status",
      +  "scheduled_at",
      +  "trigger_only_during_business_hours",
      +  "audience",
      +  "inbox",
      +  "sender_name",
      +  "use_bot_identity"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the returned content (inbox, schedule, status) but says nothing about pagination, result size or ordering, leaving meaningful behavioral gaps for a list operation.

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 short sentences, front-loaded with the scope and followed by the usage cue. There is no redundant or filler wording.

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?

For a simple, annotation-rich list tool with no output schema, the description covers purpose, returned content and usage context. It could go further by noting pagination or result limits, but nothing essential to invoking it correctly is missing.

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% and the single optional 'fields' parameter is fully documented with an enum of selectable fields. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('List the campaigns of this account') and adds what each record contains: inbox, schedule and status. It does not differentiate itself from sibling campaign listers such as list_voice_campaigns or list_whatsapp_campaigns, so it falls short of a 5.

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 explicit workflow guidance: 'Call before changing or deleting one,' which tells the agent this is a prerequisite read. It offers no exclusions or alternative-based routing, but the when-to-use context is clear.

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