Skip to main content
Glama
Sign In

flayr

by social.flayr
OverviewDiscussionsAdmin

Posts worth boosting

ads_boost_candidates
Read-onlyIdempotent

[read-only] The brand's published posts ranked for a boost (reach, engagement rate, link clicks, recency), with score parts, the call-to-action link found, and whether an ad account is connected for the network. Removed posts, posts with no call to action and networks a boost can't run on are left out. Read-only: nothing is boosted or charged. (Wraps GET /api/v2/ads/boost-candidates.)

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_boost_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to read (clamped).
limitNoHow many candidates to return (clamped).
brandIdNoA brand id from GET /api/v2/brands. Omitted: the key's brand (a brand-bound key) or the owner's active brand.
includeNoAlso list posts on networks a boost can't run on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true and destructive=false, so the safety profile is covered. The description adds genuinely new behavioral detail beyond that: the filtering rules that suppress candidates, and the fact that no ad is created or charged. With no output schema, it usefully previews the return contents.

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

Conciseness5/5

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

The key purpose and ranking signals are front-loaded in the first clause, followed by exclusion rules and a one-line read-only reassurance. There is mild overlap between the '[read-only]' tag and the closing 'Read-only:' sentence, but both are short and no sentence is wasteful.

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 four-parameter, no-output-schema read tool, the description covers what is returned, what is filtered out, and the safety profile. The only gap is that it does not tie the include parameter to the exclusion rule explicitly, but an agent has enough to call it correctly.

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 description coverage is 100%, so all four parameters are already documented, making 3 the baseline. The description hints at the include=unboostable behavior via the 'networks a boost can't run on' clause, but it does not add syntax, defaults, or edge-case semantics beyond the schema.

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

Purpose5/5

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

The description names a specific resource and operation: the brand's published posts ranked as boost candidates, and it enumerates the ranking signals (reach, engagement rate, link clicks, recency). It also lists what the response carries (score parts, CTA link, ad-account connectivity), which clearly separates it from siblings like ads_insights or ads_offers_list.

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 exclusion rules (removed posts, posts with no CTA, unsupported networks) tell an agent what this tool will not return, which is strong context for deciding to call it. It stops short of naming an alternative or explicitly stating when not to use it, so it falls just below the top band.

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

All flayr toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources