Skip to main content
Glama

Record a boost's numbers

boost_record

Record what the platform's Ads Manager shows for a boost, read in the founder's Chrome: per post or ad (n, the ad group's or ad set's number in the plan; a split boost per ad group, with device desktop or phone) the spend in USD (an account billing in another currency: converted at today's rate), impressions, and link clicks, not all clicks (engagements for a reach boost). status running when the founder has pressed Launch or Publish, stopped when they stop it. Reddit and Google, where your browser cannot go, or a TikTok export: pass the founder's export as csv (Reddit Ads, Reports, by ad group, Export; TikTok Ads Manager, the campaign's Ad group tab, Export, with Cost, Impressions and Clicks (destination); Google Ads, Campaigns, Download) and the server reads each ad group named "ad ", or Google campaign named sf-boost-- (spend or cost, impressions, clicks; daily rows added up), with usdRate when the account bills in another currency; numbers in posts win over it. Never invent a number: leave out what you could not read. Free.

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": {
      "id": "<id>"
    },
    "name": "boost_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
csvNoThe Ads Manager export, pasted as it is, broken down by ad group
postsNo
statusNo
captureNoThe phone capture's PR is merged for this boost: where its emails go, own (the founder's list or email provider) or shipfound (setup_link user events on their Users page). The signup follow-up picks these people up
usdRateNoUSD per unit of the account's currency, for the export's spend; default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / capture
      Added value: +{
      +  "description": "The phone capture's PR is merged for this boost: where its emails go, own (the founder's list or email provider) or shipfound (setup_link user events on their Users page). The signup follow-up picks these people up",
      +  "enum": [
      +    "own",
      +    "shipfound"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / posts / items / properties / device
      Added value: +{
      +  "description": "A split boost's ad group: ad <n> desktop or ad <n> phone",
      +  "enum": [
      +    "desktop",
      +    "phone"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / posts / maxItems
      Previous value: -3New value: +6
  3. Changed2 schema fields changed
    • addedInput schema / properties / csv
      Added value: +{
      +  "description": "The Ads Manager export, pasted as it is, broken down by ad group",
      +  "maxLength": 100000,
      +  "type": "string"
      +}
    • addedInput schema / properties / usdRate
      Added value: +{
      +  "description": "USD per unit of the account's currency, for the export's spend; default 1",
      +  "type": "number"
      +}
  4. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this writes data without being destructive. The description adds useful behavior beyond that: currency is converted at today's rate, exports are parsed by ad-group naming conventions, and unreadable values must be omitted. But it does not say whether a repeat call overwrites previously recorded numbers or how conflicts between existing records and new input are handled, a significant gap for a write tool.

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?

It is one dense paragraph of long parenthetical-clause sentences that are hard to parse on first read, though the essential instruction about what to record comes first. Most content earns its place, but the density hurts usability.

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 six-parameter write tool with no output schema, it covers data sources, currency handling, export formats, status semantics, and the no-invention safeguard. Remaining gaps are the semantics of repeated writes and any mention of the capture parameter's effect.

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 description coverage is only 50%, so the description has to compensate and does: it explains the csv format (Reddit Reports by ad group, TikTok Ad group tab with Cost/Impressions/Clicks, Google Campaigns download), how ad groups are matched ('ad <n>' or 'sf-boost-<id>-<n>'), that daily rows are summed, and how usdRate 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?

The description opens with a concrete verb and resource: 'Record what the platform's Ads Manager shows for a boost', and it names the exact metrics (spend in USD, impressions, link clicks) and status values that get stored. An agent can distinguish this from siblings such as boost_results or boost_check, though the description never names an alternative tool, so it falls 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 Guidelines4/5

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

It gives clear conditions for the two input paths: read numbers from Chrome when the platform is Facebook, and pass the founder's export as csv for Reddit, Google, or TikTok. It also sets precedence ('numbers in posts win over it') and an explicit rule ('Never invent a number: leave out what you could not read'), but it does not state when to use this instead of a sibling such as boost_results.

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