Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

ad_manager_fb_pause_ad

Pause a Facebook ad by supplying its ad ID to halt delivery and control campaign spending.

Instructions

Pause ad

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adIdYes
locationIdNoLocation identifier Defaults to GHL_LOCATION_ID when omitted.
Behavior2/5

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

The description does not contradict the annotations (readOnlyHint=false, destructiveHint=false), but it adds no behavioral detail beyond what the name implies. It fails to disclose side effects, whether pausing is reversible, or any permission requirements, despite openWorldHint=true.

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

Conciseness2/5

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

The description is extremely short, but this is under-specification rather than conciseness. It lacks essential information that could be conveyed in a few sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with two parameters and no output schema, the description is completely inadequate. It does not explain what pausing an ad entails, what state changes occur, or any expected outcomes, leaving the agent to guess.

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

Parameters1/5

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

The description does not mention any parameters. The schema covers only 50% of parameters (locationId has a description, adId does not), and the description adds nothing to help an agent understand what adId refers to or how it should be supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Pause ad' is essentially a tautology of the tool name. It states the verb and resource but provides no scope, context, or differentiation from similar tools like ad_manager_fb_pause_adset and ad_manager_fb_pause_campaign, which are siblings.

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

Usage Guidelines1/5

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

No guidance is given on when to use this tool versus alternatives such as pausing an ad set or campaign, or resuming an ad. There is no mention of prerequisites, context, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIWerk/mcp-server-ghl'

If you have feedback or need assistance with the MCP directory API, please join our Discord server