Skip to main content
Glama

Shipfound

by co.shipfound.api
OverviewDiscussionsAdmin

Ad account and tracking

ads_setup

Where an ad platform (x, meta, reddit 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 X's click id. 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; 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_; 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.

Input Schema

NameRequiredDescriptionDefault
recordNo
platformNoDefault x

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
+}
  3. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations mark this as mutating-capable (readOnlyHint=false) but non-destructive; the description supplements this usefully by explaining the two modes: a read that returns step states plus optimisation hints, and a 'record' that writes what you read. It also gives platform-specific sources (ads.x.com, business.facebook.com, ads.reddit.com, ads.google.com) and concrete 'verified' criteria, which is real behavioural 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 whole definition is one massive, comma-spliced paragraph with an embedded numbered list and a field dump. It is front-loaded with purpose but not structured for parsing, and several clauses (cross-referencing URLs and values) could be scoped to the parameters instead of the body. Length is justified by complexity, but presentation is poor.

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 nested, mutation-capable tool with no output schema, the description does well: it states what is returned (each step's state, optimisation options, recommended ladder step, goals with firability, clicksSeen) and what record persists per platform. The main gap is the absence of a return shape or failure/edge handling, but overall an agent has enough to 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?

Schema coverage is only 50% and the record object is deeply nested, so the description carries heavy load: it explains the meaning of account fields per platform (payment method, business portfolio, Page picture), the tracking pixelId format per platform (X pixel id, Meta dataset id, Reddit a2_/t2_, Google AW- conversion ID with label as event), and the 'verified' semantics. This meaningfully compensates for the schema gap, though some field-level precision still lives only in the schema descriptions.

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 names the resource (ad-platform setup state for a boost) and enumerates the three steps it reports (account, tracking, launch), plus a record mode. However, the purpose is buried inside a dense run-on sentence, and it never cleanly distinguishes itself from near-neighbours like tracking_check, launch_prep, or ads_propose. It is decipherable but not crisp.

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?

There is no explicit 'use this when / not when' guidance and no siblings are named as alternatives. A reader can infer it is the setup-status tool, but nothing routes the agent between ads_setup, tracking_check, tracking_install, and launch_prep. The record mode is described mechanically but not framed as a when-to-use decision.

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

All Shipfound toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources