Skip to main content
Glama

Ad account and tracking

ads_setup

Where an ad platform (x, meta, reddit, tiktok or google) stands for a boost, in the fixed order: 1. account (an ad account with a payment method the founder added, read in their browser; on Meta first a business portfolio and the Facebook Page the ads run under, with its own profile picture), 2. tracking (the platform's pixel on the site, loaded by Shipfound's script, so the founder deploys nothing: the pixel id and an event per ladder step, read in Events manager), 3. launch. Returns each step's state and what to do, what the campaign can optimise for, the recommended step of the ladder (landing page view, signup, payment: the deepest with enough volume) for the founder to confirm, the site's signup and payment goals (firable: whether the pixel can see them in the browser), and clicksSeen: visits in the last 7 days that arrived with the platform's click id. appTraffic: TikTok for an iOS app, run as traffic to the App Store link with no pixel (TikTok's app events need its SDK or a measurement partner). intent: whether a Google search test comes before a cold feed test for this product (a phone cannot take its first step, or nobody has paid yet), why in one plain line, and terms, the searches it starts from (a rival's "alternative" search, the buyer's problem, searches the site already shows for). With record, first stores what you read: account { adAccountId?, name?, payment?, currency?, businessId?, pageId?, pageName?, pagePicture? } (X: ads.x.com; Meta: business.facebook.com settings and Ads Manager; Reddit: ads.reddit.com; TikTok: the advertiser id, aadvid= in ads.tiktok.com's URL; Google: the customer ID at ads.google.com); tracking { pixelId, events?, verified? } from Events manager (X: the pixel id and each event's id; Meta: the dataset id; Reddit: the pixel id, a2_ or t2_; TikTok: the TikTok Pixel's id; their standard events need no ids; Google: the conversion ID, AW- and digits, as pixelId, and each conversion action's label, after the slash in its send_to, as the event; verified: it shows events recorded from the site, or on Google the tag shows as active). Free.

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

Input Schema

NameRequiredDescriptionDefault
recordNo
platformNoDefault x

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "x",
      -  "meta",
      -  "reddit",
      -  "google"
      -]New value: +[
      +  "x",
      +  "meta",
      +  "reddit",
      +  "google",
      +  "tiktok"
      +]
    • changedInput schema / properties / record / properties / account / properties / adAccountId / description
      Previous value: -"X: in the ads.x.com/manager/<id> URL. Meta: act= in Ads Manager's URL. Reddit: in the ads.reddit.com account URL. Google: the customer ID, 123-456-7890"New value: +"X: in the ads.x.com/manager/<id> URL. Meta: act= in Ads Manager's URL. Reddit: in the ads.reddit.com account URL. TikTok: the advertiser id, aadvid= in Ads Manager's URL. Google: the customer ID, 123-456-7890"
    • changedInput schema / properties / record / properties / tracking / properties / pixelId / description
      Previous value: -"X: the id next to \"X Pixel\" in Events manager. Meta: the dataset id. Reddit: the pixel id in Events Manager"New value: +"X: the id next to \"X Pixel\" in Events manager. Meta: the dataset id. Reddit: the pixel id in Events Manager. TikTok: the TikTok Pixel's id in Events Manager"
  2. Changed2 schema fields changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "x",
      -  "meta",
      -  "reddit"
      -]New value: +[
      +  "x",
      +  "meta",
      +  "reddit",
      +  "google"
      +]
    • changedInput schema / properties / record / properties / account / properties / adAccountId / description
      Previous value: -"X: in the ads.x.com/manager/<id> URL. Meta: act= in Ads Manager's URL. Reddit: in the ads.reddit.com account URL"New value: +"X: in the ads.x.com/manager/<id> URL. Meta: act= in Ads Manager's URL. Reddit: in the ads.reddit.com account URL. Google: the customer ID, 123-456-7890"
  3. Changed2 schema fields changed
    • addedInput schema / properties / record / properties / account / properties / pagePicture
      Added value: +{
      +  "description": "Meta: the Page shows its own profile picture (the product's logo or icon), not the blank default",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / record / properties / account / properties / profile
      Added value: +{
      +  "description": "Reddit: the profile the ads post under, assigned to the ad account",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  4. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already state that this is a non-read-only, open-world, non-destructive tool. The description adds meaningful behavior: it explains the account, tracking, and launch state model, the recommendation it returns, clicksSeen, appTraffic handling, and that the record branch stores the values the user read. It still leaves some mutation details implicit, but it adds substantial context beyond 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.

Conciseness2/5

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

The description is a dense, run-on block with nested parentheticals and semicolon-separated platform details. It is front-loaded around a workflow, but the wall-of-text structure makes it hard to scan and separates critical distinctions, such as read versus record behavior, from the reader.

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 complex nested tool with no output schema, the description does cover many platform-specific details and the main return concepts. However, it remains ambiguous about the exact response shape, when record is expected, and how the tool behaves when no record is supplied, leaving notable gaps for an agent that must invoke it correctly.

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

Parameters4/5

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

The schema covers only about half the parameters, but the description compensates heavily by explaining account and tracking fields with platform-specific meanings, including ad account ID formats, pixel IDs, event IDs, and verification semantics. It does not cover every schema field equally, such as profile, but it adds far more semantic meaning than the raw schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this tool checks where an ad platform stands in the account-tracking-launch sequence and can optionally record what was read. However, it opens with conceptual phrasing rather than a crisp verb and resource, and it never names sibling tools such as tracking_check or boost_plan to sharpen its purpose.

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?

It describes a setup process and some return details but gives no explicit guidance on when to call this tool versus alternatives. There are no when-not conditions, prerequisites, or named sibling tools, so the agent must infer usage from the surrounding workflow.

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