Skip to main content
Glama
Mike25app

scaleforge-mcp-meta-ads

update_bids_batch

Update bid amounts on multiple ad sets in a single Batch API call. Provide pairs of ad set IDs and bid values in cents. Automatically handles batches of 50.

Instructions

WRITE (BULK): Update bid_amount on many ad sets in one Batch API call. Input is an array of {adset_id, bid_amount_cents} pairs. Bid values are in minor currency units (cents). Chunks of 50 automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatesYesArray of {adset_id, bid_amount_cents} to apply
Behavior3/5

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

Without annotations, the description carries the burden. It discloses auto-chunking of 50 and that it's a WRITE operation, but does not mention idempotency, failure handling, or permission requirements. Adequate but not comprehensive.

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?

Two sentences, immediately labeling the tool as 'WRITE (BULK)' and front-loading the verb and resource. No wasted words.

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

Completeness3/5

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

No output schema. The description covers the input format and batch behavior but lacks information about return values, error handling, or success confirmation. Adequate for a simple bulk update tool but could be more complete.

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 100%, so baseline is 3. The description adds value by specifying that bid values are in minor currency units (cents) and that chunks of 50 are automatically handled, which goes beyond the schema's parameter description.

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 clearly states 'Update bid_amount on many ad sets' with a bulk WRITE annotation. It distinguishes from sibling tools like update_adset (single) by explicitly stating 'BULK' and 'many ad sets'.

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 clearly indicates when to use this tool (bulk updates to bid_amount) and implies it's for multiple adsets, distinguishing from single-update tools. However, it does not explicitly exclude single-adset use or mention update_adset as an alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mike25app/scaleforge-mcp-meta-ads'

If you have feedback or need assistance with the MCP directory API, please join our Discord server