Skip to main content
Glama

List Ad Operations

postly_list_ad_operations
Read-onlyIdempotent

Lists the 30 most recent ad creations and changes made through Postly for an ad account, with their status and result. Use it to check an operation from postly_apply_ad. Requires ads.read.

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>"
    },
    "name": "postly_list_ad_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesAds network from postly_list_ad_accounts, such as google or meta.
account_idYesNative ad account ID from postly_list_ad_accounts.
workspace_idYesPostly workspace ID.

Output Schema

NameRequiredDescriptionDefault
codeNo
dataNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: the result set is capped at the 30 most recent operations and the call requires the ads.read scope. It does not say whether older operations are retrievable at all, a minor residual gap.

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 short sentences, zero filler, with the scope and the 30-item cap front-loaded before the usage hint and the permission requirement.

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 read-only list tool with full annotation coverage, a complete output schema, and fully described parameters, the description supplies everything else an agent needs: what is listed, the cap, the return fields, the auth scope, and the paired write tool.

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% with all three parameters documented and cross-referenced to postly_list_ad_accounts, so the schema does the heavy lifting. The description only implies that the list is scoped 'for an ad account' without adding syntax or constraint detail beyond the schema; baseline 3 applies.

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 and resource ('Lists the 30 most recent ad creations and changes') with an explicit scope cap of 30 and the fields returned (status and result). An agent can distinguish this audit-style operation log from postly_list_ads or postly_get_ads_overview 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 Guidelines4/5

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

'Use it to check an operation from postly_apply_ad' gives a concrete routing rule tied to a named sibling tool. There is no explicit when-not guidance (e.g., use postly_list_ads to see live ad entities instead of operations), which keeps it just short of a 5.

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.

Resources