activate_ad_group
Re-enable a paused ad group by providing its ID to resume ad delivery and campaign performance.
Instructions
Activate a paused ad group.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ad_group_id | Yes | Ad group ID. | |
| ad_account_id | No |
Re-enable a paused ad group by providing its ID to resume ad delivery and campaign performance.
Activate a paused ad group.
| Name | Required | Description | Default |
|---|---|---|---|
| ad_group_id | Yes | Ad group ID. | |
| ad_account_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'activate' and 'paused' without explaining prerequisites, consequences, reversibility, idempotency, or failure behavior. The state qualifier is mildly informative but far from sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. The word 'paused' earns its place by clarifying the target state. It is concise, though it sacrifices behavioral and contextual detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a mutating tool with no annotations and no output schema. The one-line description does not explain preconditions such as whether the ad group must exist and be paused, what happens after activation, or whether ad_account_id is needed. An agent is not given enough context to invoke it confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 50%; ad_account_id has no schema description and the tool description does not mention it. The description adds no meaning to the parameters beyond what the schema already provides, so it fails to compensate for the undocumented parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Activate a paused ad group.' This clearly identifies the operation and narrows the target state to paused ad groups, though it does not explicitly call out sibling tools such as activate_campaign or pause_ad_group.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The qualifier 'paused' implies this tool should be used when an ad group is currently paused, but there is no explicit when-to-use guidance, no mention of alternatives, and no statement about when this tool should not be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/niyogi/chatgpt-ads-manager-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server