Skip to main content
Glama

oriiion

pause_chatgpt_ad

Pause delivery of the current user’s ChatGPT ad. It can be resumed with start_chatgpt_ad before its deadline and within the remaining budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, non-idempotent write, so the safety profile is covered. The description adds genuinely useful behavior: the pause is reversible via start_chatgpt_ad and is bounded by a deadline and remaining budget.

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?

Two compact sentences, front-loaded with the action, no filler. The resume detail is placed second, which is the right order.

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?

Covers reversibility and constraints, which matters for an unannotated-output mutation tool, but omits the sole parameter's meaning and the pause-vs-end distinction in a sibling set containing end_chatgpt_ad.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single required campaignId, and the description says nothing about it. Worse, 'the current user's ChatGPT ad' implies implicit targeting, which conflicts with the schema's requirement to pass an explicit campaignId.

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 (Pause) and resource (ChatGPT ad) with clear scope (the current user's ad). It names start_chatgpt_ad as the resume path, but does not distinguish itself from the sibling end_chatgpt_ad, which also stops an ad and could be confused with pausing.

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

Usage Guidelines3/5

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

The description gives conditions for resuming (before deadline, within remaining budget), which implies pause is a temporary, recoverable action. It never says when to pause rather than end the ad, nor what prerequisites exist, leaving the key routing decision to inference.

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