Postly MCP

Apply Ad

postly_apply_ad

DestructiveIdempotent

Publishes a reviewed ad campaign or change from postly_prepare_ad to the ad network. This can spend money. Call only after the user explicitly confirms that exact summary. Repeating the call returns the same operation instead of creating a duplicate. If the result needs attention, check the native ads account and postly_list_ad_operations before trying again. Only workspace Owners and Admins can create or change ads with AI agents. Requires ads.write.

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": {
      "workspace_id": "<workspace_id>",
      "provider": "<provider>",
      "account_id": "<account_id>",
      "operation_id": "<operation_id>"
    },
    "name": "postly_apply_ad"
  }
}

Input Schema

Name	Required	Description
`provider`	Yes	Ads network from postly_list_ad_accounts, such as google or meta.
`account_id`	Yes	Native ad account ID from postly_list_ad_accounts.
`operation_id`	Yes	The id returned by postly_prepare_ad.
`workspace_id`	Yes	Postly workspace ID.

Output Schema

Name	Required	Description	Default
`code`	No
`data`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructive, open-world, idempotent, and non-read-only behavior, but the description adds critical context beyond them: the operation can spend money, requires explicit user confirmation, returns the same operation on repeat calls, and requires Owner/Admin permissions plus ads.write. These are high-value operational constraints for a financially sensitive mutation.

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 description is front-loaded with the action and financial risk, then proceeds through confirmation, idempotency, troubleshooting, and permissions. Every sentence carries operational weight for a destructive, money-spending tool, so the length is justified.

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?

Given that an output schema exists, return values need not be explained. The description covers the key complexities—financial risk, confirmation requirement, idempotency, permissions, and troubleshooting—so an agent has what it needs to invoke the tool safely.

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 coverage is 100%, so all four parameters are already documented in the input schema. The description references postly_prepare_ad as the source of operation_id, but adds no syntax or meaning beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb ('Publishes') and resource ('reviewed ad campaign or change from postly_prepare_ad to the ad network'), clearly positioning it as the apply step after postly_prepare_ad. This distinguishes it from preparation and listing siblings without needing to inspect schemas.

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?

It gives explicit when-to-use guidance: 'Call only after the user explicitly confirms that exact summary.' It also covers retry behavior and points to postly_list_ad_operations when a result needs attention, effectively routing the agent among alternatives.

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

All Postly MCP tools Inspect

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

Need Help?