Skip to main content
Glama

Meta: cap how often one person sees the ads

meta_set_frequency_cap
DestructiveIdempotent

Cap how often one person sees a Meta ad set's ads: at most N impressions per person per day, week or month. Meta takes a cap only on ad sets optimised for reach or ThruPlay; on any other goal it decides how often, and the answer says what to do instead (fresh ads, a wider audience). Call without confirm first: Meta checks the change (validate only) and nothing changes. remove: true takes the cap off.

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": {
      "adset_id": "<adset_id>"
    },
    "name": "meta_set_frequency_cap"
  }
}

Input Schema

NameRequiredDescriptionDefault
removeNoTake the ad set's cap off
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
adset_idYes
frequency_capNoe.g. {impressions: 2, per: 'week'}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, openWorldHint=true) it discloses the goal-based eligibility constraint and that a confirm=false call is a validate-only preview that changes nothing. It does not say what happens to an existing cap when a new one is set, nor what the preview payload contains, so it adds context without fully covering mutation semantics.

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

Conciseness4/5

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

Four sentences, front-loaded with the core effect, then eligibility, then the confirm workflow, then remove. Dense but every sentence carries signal; no filler.

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?

With a nested frequency_cap object, 75% schema coverage and no output schema, the definition covers the main call path but leaves gaps: a nested-object example is only in the schema, and the actual response/preview contents are alluded to rather than characterised.

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?

Clarifies behaviour of the two ambiguous booleans: confirm is a preview switch, and remove strips the cap. It restates the frequency_cap shape (impressions per person per day/week/month) already in the schema, but adds the intent-level meaning of the options rather than just repeating them.

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?

States a specific verb and resource ('Cap how often one person sees a Meta ad set's ads') and quantifies the effect (N impressions per person per day/week/month). It is unambiguous on its own, though it never names the closely-named sibling ads_set_frequency_cap to distinguish the two.

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?

Gives a real eligibility rule: Meta honours a cap only on ad sets optimised for reach or ThruPlay, and on other goals the answer redirects to fresh ads or a wider audience. It also prescribes the calling workflow ('Call without confirm first'). Missing only explicit steering toward a sibling tool for the ineligible-goal case.

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.