Skip to main content
Glama

Read a boost

boost_results
Read-only

A boost against its stop rule and, with several posts, against each other: each post's click rate, cost per click, cpmUsd (cost per 1,000 impressions), and the visits and signups its tagged link brought; costAlarm when an ad pays over twice the top of the platform's CPM range after $10, with the likely setup causes; taggingNote when the platform shows clicks but few or no visits carry the boost's tags; the verdict (not launched, needs numbers, too early, stop, winner, no clear winner, working, lost after click: people clicked and none signed up). A winner is called only at a 90% chance of being the best, once each post has 1,500 impressions; on signups once there are 5, else on clicks. path: the visits past the click (stayed, reached the signup page, signed up, paid), by phone and desktop, against the site's usual engaged rate; diagnosis: the step that lost people (message, page, device, signup, or holding) and its next move; devicesNote: a split boost's desktop and phone ad groups side by side; retarget: whether enough visits did not sign up to offer the optional retargeting ad (the platform's minimum audience over the half its pixel matches: 200 visits on X and Meta, 2,000 on Reddit and Google), which then comes before a new cold test; clickStop: 150 ad clicks or more and nobody through the conversion step (a signup, or the phone capture's email), so stop and fix the page or the audience, never a refresh. Without id, the latest boost. With history true, instead every boost launched before: its posts' links and words, where it went and its verdict, so a new boost tests something new. 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": "boost_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
historyNoEvery boost launched before, instead of one read-out

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / history
      Added value: +{
      +  "description": "Every boost launched before, instead of one read-out",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds that the call is 'Free' and, with no output schema, carries the burden of describing return content and the decision thresholds behind each field (1,500 impressions, 90% confidence, 150 ad clicks, 200/2,000 visit audience minimums) — genuinely useful behavior-level context, but permissions and result shape remain undisclosed.

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 content is one unbroken paragraph of roughly 250 words with nested parentheticals (verdict lists, audience minimums, threshold conditions), which makes it hard to scan. The parameter guidance an agent needs before calling sits at the very end rather than being front-loaded.

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 two optional parameters, no output schema and read-only annotations, the definition covers what is needed: what each returned field means, the thresholds that trigger each verdict, and the id/history switching. Minor gaps remain around response ordering or size for the history mode.

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% (id has no schema description), and the description compensates: it states that omitting id reads the latest boost, and that history true switches the whole response from a single read-out to a cross-boost history with links and verdicts. That is meaning well beyond the boolean/string types.

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 specific resource (a boost) and enumerates exactly what a read-out contains — per-post click rate, CPC, cpmUsd, visits, signups, verdict, path, diagnosis, retarget, clickStop — which clearly separates it from siblings like boost_check, boost_plan, boost_record and boost_change. It lacks an explicit leading verb (it opens as an elliptical noun phrase, 'A boost against its stop rule and ...'), so the 'read' framing relies partly on the title.

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?

The closing clauses give concrete selection rules: omit id to read the latest boost, and set history true to get every prior boost (links, words, destination, verdict) 'so a new boost tests something new' — implying use before launching a new test. There is no explicit when-not clause or named alternative among the siblings, so it stops short of full routing guidance.

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