Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

ad_manager_fb_pause_adset

Pause a Facebook ad set by ID to halt delivery and control campaign spend.

Instructions

Pause ad set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adsetIdYes
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 discloses no behavioral traits beyond the fact that it pauses an ad set, which is inherent to the name. While annotations indicate it is not read-only (readOnlyHint=false) and not destructive, the description adds no detail on side effects, permissions, or impact on related entities, leaving the agent with insufficient insight.

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?

While the description is extremely short, it is under-specified rather than concise. It lacks any structural elements such as context, examples, or necessary caveats, and fails to front-load critical information an agent would need.

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?

The description is severely incomplete for a mutation tool. It does not mention return values, side effects, required permissions, or how to obtain the adsetId. With no output schema and minimal annotations, the description leaves the agent without enough information to call the tool correctly and confidently.

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?

The description adds no meaning to the parameters. One parameter (locationId) has a schema description, but adsetId is undocumented. The description does not explain what an adsetId is or how to obtain it, and does not compensate for the 50% schema coverage gap.

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?

The description 'Pause ad set' clearly states the verb (pause) and resource (ad set), making the action unambiguous. However, it does not differentiate from sibling tools like ad_manager_fb_pause_ad or ad_manager_fb_resume_adset, relying entirely on the tool name for that distinction.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives, no prerequisites, and no context about the state changes involved. The description provides no help in selecting this tool over pause_ad, pause_campaign, or others.

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