Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_page_posts_boost

Boost an existing Facebook Page post by creating a paid ad from it, reusing the post as creative and attaching it to an existing ad set. Returns the new ad ID.

Instructions

Boosts an existing Facebook Page post by creating a paid ad that uses the post as its creative. Returns the new ad_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. The parent ad_set_id must already exist with budget and targeting configured — this tool only attaches the post as creative. For new-creative paid ads use meta_ads_ads_create with a creative_id instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAd name shown in Ads Manager. Auto-generated from the post if omitted.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
page_idYesFacebook Page ID that owns the post.
post_idYesPost ID as returned by meta_ads_page_posts_list. Post must be public and compatible with Ads eligibility policies.
ad_set_idYesParent ad set that will carry the boosting ad. Must already exist with budget and targeting.
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of disclosure, and it delivers: labels the operation as mutating, says it is not automatically reversible, recommends recording before-state with mureo_state_action_log_append, and notes the prerequisite dependency on the ad set. It does not address permissions or failure modes, but the core behavioral traits are clearly covered.

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?

Four sentences, each earning its place: the action and return value are front-loaded, the mutation warning follows immediately, then the prerequisite and alternative are clearly separated. No filler or repetition of schema text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with six parameters, no output schema, and no annotations, the description is complete: it explains the returned ad_id, the required preconditions, the rollback path via mureo_state_action_log_append, and the sibling alternative. An agent can correctly decide to invoke it and knows what to expect as a result.

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%, with detailed per-parameter descriptions already provided, so the baseline is 3. The description adds useful context about the ad_set_id role (must already exist with budget/targeting) and that the post is attached only as creative, but it does not add much beyond what the schema already encodes.

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?

States a specific verb ('Boosts') and resource ('existing Facebook Page post'), then clarifies the mechanism: creating a paid ad that uses the post as creative. It also names an alternative sibling (meta_ads_ads_create) for the new-creative case, so an agent can distinguish it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly tells when to use this tool − only when boosting an existing post as creative − and points to meta_ads_ads_create with a creative_id when that condition does not hold. It also states the prerequisite that ad_set_id must already exist with budget and targeting configured, giving clear operational guidance.

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

Deploy Server

Other Tools