Skip to main content
Glama

ADS Beast

list_campaigns

Read-only

Return campaigns from every connected advertising platform in one list, with their status, budget and platform ids. Archived campaigns are left out unless include_archived is true.

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
limitNoPage size. Clamped into 1..2000 before the request. A page is also cut to fit the response size limit; when the reply has has_more = true, call again with offset = next_offset.
offsetNoPagination offset. The reply carries total.
platformNoRestrict to one platform. Omit for all platforms.
client_idNoRestrict to one client.
include_archivedNoTrue also returns archived campaigns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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=true, so safety is covered. The description still adds real value beyond them: archived campaigns are silently excluded by default, and the result shape (status, budget, platform ids) is disclosed. Pagination/rate-limit behavior is left entirely to the schema.

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 with zero filler: the capability and scope lead, and the archived-exclusion caveat follows. Every clause carries information an agent needs.

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?

With five optional params, full schema coverage, and no output schema, the description correctly compensates by naming the returned fields. Pagination is well handled in the schema. What's missing is any hint of result volume or how 'connected platforms' affects the call, but nothing essential to invoking it is absent.

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 every parameter including limit, offset, platform, client_id and include_archived is documented in the schema. The description restates the include_archived default but adds no syntax, format, or interaction detail beyond what the schema already gives, so baseline 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 ('Return') and resource ('campaigns'), plus scope ('from every connected advertising platform in one list') and the fields returned (status, budget, platform ids). That scope implicitly separates it from siblings like list_outreach_campaigns or list_social_campaigns, but no sibling is named, so it stops 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 Guidelines3/5

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

The cross-platform ad-campaign scope implies when to reach for this versus the outreach/social/draft listers, and the archived-default note gives a conditional behavior. However, there is no explicit when-to-use/when-not statement and no alternative tool is named for narrower cases.

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.