Skip to main content
Glama
adpilot-mcp

adpilot-mcp

Official
by sholaxai

list_campaigns

Read-only

Retrieve campaigns across connected ad platforms with their status and daily budget, filtered by active, paused, or all, to review and manage ad spend.

Instructions

List every campaign across connected ad platforms with status and daily budget.

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
statusNoALL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful scope by saying it lists campaigns across connected ad platforms and includes status and daily budget, but it does not disclose pagination, ordering, or whether archived campaigns are included.

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?

The definition is a single front-loaded sentence with no wasted wording. It places the scope, resource, and returned fields in one efficient statement.

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 simple read-only list with one optional filter and no output schema, the description covers the core action and returned fields. However, it omits how the status filter works and whether results are paginated or aggregated across platforms, which leaves meaningful gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single status parameter has an enum and a default but zero schema description coverage, so the description must compensate. Instead, "with status" reads more like a returned field than a filter, and the description never explains ACTIVE, PAUSED, ALL, or the default behavior.

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 uses a clear verb, "List," and a specific resource, "every campaign across connected ad platforms," plus the returned fields status and daily budget. It does not explicitly differentiate this inventory listing from campaign_performance or set_campaign_status, but the core purpose is clear.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no exclusions, and no alternatives. It does not explain when to choose this listing over campaign_performance or set_campaign_status, leaving usage to inference.

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