Skip to main content
Glama

Campaigns setup

campaigns_setup
Read-onlyIdempotent

Reads the Meta account settings a new launch or a read-only launch check needs: the selected Meta accounts with internal accountId, currency, snapshot freshness and available Page IDs, the account's datasets (pixels) as the editor lists them, the datasets its ad sets optimize for (adSetDatasetIds), and image hashes. Edits to what already runs (budget, bid, status, placements, audience, dates, copy) take their ids from campaigns_structure. Candidates listed here are not confirmed selections, permission or event checks, or a passed preflight. Without an explicitly scoped account it returns the accounts to pick from. An empty asset list means media has to be uploaded, or an identity connected, in Adrails Campaigns. Read only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "campaigns_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. 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, idempotentHint=true and openWorldHint=false, and the closing "Read only" merely restates them. The description earns credit elsewhere: it discloses that candidates are not confirmed selections, permission or event checks, or a passed preflight, and it explains two non-obvious return behaviors (unscoped calls return the account picker; an empty asset list means media must be uploaded or an identity connected in Adrails Campaigns). That is real behavioral context an agent cannot derive from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded but overstuffed, packing five distinct asset categories into one comma-chained clause, and the cautions that follow arrive as a dense run of clauses of equal weight. No sentence is truly wasted, but the wall-of-nouns style makes the key routing signal (read here before editing via campaigns_structure) harder to extract than it should be.

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 four parameters, nested input, no output schema and rich annotations, the description covers what the tool returns and what its empty/unscoped results mean, so an agent can call it and interpret the response correctly. The remaining gap is that it frames the tool as reading "Meta account settings" while the platform enum also accepts google_ads, and it never mentions userStatement or idempotencyKey.

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 coverage is 75%, so the baseline is 3, and the description adds little beyond the schema for parameters. It clarifies what an omitted account scope yields (returns the accounts to pick from), which is genuine added meaning for accountIds, but userStatement, idempotencyKey and the platform enum are untouched in the description. The one link it does make — platform choosing which accounts appear — is already in the schema text.

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 names a concrete verb ("reads") and enumerates the specific resources: selected Meta accounts with internal accountId, currency, snapshot freshness, Page IDs, datasets, adSetDatasetIds and image hashes. It also explicitly carves out a boundary against campaigns_structure, which handles edits to running entities. What keeps it from a 5 is that the tool name ("campaigns_setup") suggests campaign creation, while the body describes a read of account/asset configuration, so the label and content pull in slightly different directions.

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?

It states the trigger conditions precisely: "a new launch or a read-only launch check," and points to campaigns_structure for the edit path, so the primary routing decision is explicit. It does not address other plausibly competing siblings (accounts_list, campaign_media, editor_settings_reference, targeting_options), so the agent still has to infer where the boundary lies with those.

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.