Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

ad_manager_fb_resume_campaign

Resume a paused Facebook ad campaign using its campaign ID and optional location ID within GoHighLevel.

Instructions

Resume campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYes
locationIdNoLocation identifier Defaults to GHL_LOCATION_ID when omitted.
Behavior1/5

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

The description discloses no behavioral traits beyond what annotations already imply. Annotations (readOnlyHint=false, destructiveHint=false) are minimal, and the description adds nothing about what resuming entails—side effects, state changes, or expected outcomes. It completely fails to enrich understanding.

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?

Two words is under-specification, not conciseness. It is too terse to be useful and skips essential information. While front-loading is not an issue, the content is practically absent.

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 tool that mutates state (resuming a campaign) with no output schema, the description is severely incomplete. It lacks any explanation of side effects, return values, or interaction with the broader ad manager system. It is inadequate for an agent to call correctly.

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 tool description provides no explanation of campaignId or locationId. While the schema has a description for locationId (50% coverage), the tool description does not compensate for the undocumented campaignId or clarify parameter relationships. Schema coverage is moderate but the description adds zero value.

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 'Resume campaign' is essentially a tautology—it repeats the action implied by the tool name without adding any specific resource context or differentiating it from siblings like ad_manager_fb_pause_campaign or ad_manager_fb_publish_campaign. It states a verb and object but offers no distinction.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., needing an active integration or paused campaign), and no exclusions. The description provides absolutely no context for selection.

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